zpwiki/pages/topics/question
2021-02-23 08:38:14 +01:00
..
navod zz 2021-02-23 08:38:14 +01:00
README.md Update 'pages/topics/question/README.md' 2021-01-26 13:40:07 +00:00

title published taxonomy
Question Answering true
category tag author
project
annotation
question-answer
nlp
Daniel Hladek

Question Answering

Project Description

Auxiliary tasks:

  • Consider using machine translation
  • Train and evaluate Question Answering model

People

  • Daniel Hládek (responsible researcher).
  • Tomáš Kuchárik (student, help with web app).
  • Ján Staš (BERT model).
  • Ondrej Megela, Oleh Bilykh, Matej Čarňanský (auxiliary tasks).
  • other students and annotators (annotations).

Tasks

Raw Data Preparation

Input: Wikipedia

Output: a set of paragraphs

  1. Obtaining and parsing of wikipedia dump
  2. Selecting feasible paragraphs

Done:

  • Wiki parsing script (Daniel Hládek)
  • PageRank script (Daniel Hládek)
  • selection of paragraphs: select all good paragraphs and shuffle
  • fix minor errors

To be done:

  • Select the largest articles (to be compatible with squad).

Notes:

Question Annotation

An annotation recipe for Prodigy

Input: A set of paragraphs

Output: 5 questions for each paragraph

Done:

  • a data preparation script (Daniel Hládek)
  • annotation recipe for Prodigy (Daniel Hládek)
  • deployment at question.tukekemt.xyz (only from tuke) (Daniel Hládek)
  • answer annotation together with question (Daniel Hládek)
  • prepare final input paragraphs (dataset)

In progress:

  • More annotations (volunteers and workers).

To be done:

  • Prepare development set

Annotation Web Application

Annotation work summary, web applicatiobn

Input: Database of annotations

Output: Summary of work performed by each annotator

Done:

  • application template (Tomáš Kuchárik)
  • Dockerfile (Daniel Hládek)
  • web application for annotation analysis in Flask (Tomáš Kuchárik, Daniel Hládek)
  • application deployment (Daniel Hládek)
  • extract annotations from question annotation in squad format (Daniel Hladek)

To be done:

  • review of validations

Annotation Validation

Input: annnotated questions and paragraph

Output: good annotated questions

Done:

  • Recipe for validations (binary annotation for paragraphs, question and answers, text fields for correction of question and answer). (Daniel Hládek)
  • Deployment

To be done:

  • Prepare for production

Annotation Manual

Output: Recommendations for annotators

Done:

  • Web Page for annotators (Daniel Hládek)
  • Modivation video (Daniel Hládek)
  • Video with instructions (Daniel Hládek)

In progress:

  • Should be instructions a part of the annotation webn application?

Question Answering Model

Training the model with annotated data

Input: An annotated QA database

Output: An evaluated model for QA

To be done:

  • Selecting existing modelling approach
  • Evaluation set selection
  • Model evaluation
  • Supporting the annotation with the model (pre-selecting answers)

In progress:

  • Preliminary model (Ján Staš and Matej Čarňanský)

Existing implementations

Bibligraphy

  • Reading Wikipedia to Answer Open-Domain Questions, Danqi Chen, Adam Fisch, Jason Weston, Antoine Bordes Facebook Research
  • SQuAD: 100,000+ Questions for Machine Comprehension of Text https://arxiv.org/abs/1606.05250
  • WDaqua publications

Existing Datasets

Intern tasks

Week 1: Intro

Week 2 and 3: Web Application

  • Analyze sql schema of Prodigy annotations
  • Find out who annotated what.
  • Make a web application that displays results.
  • Extend the application to analyze more Prodigy instances (for both question and answer annotations)
  • Improve the process of annotation.

Output: Web application (in Node.js or Python) and Dockerfile

Week 4-7 The model

Select and train a working question answering system

Output:

  • a deployment script with comments for a selected question answering system
  • a working training recipe (can use English data), a script with comments or Jupyter Notebook
  • a trained model
  • evaluation of the model (if possible)