-
Notifications
You must be signed in to change notification settings - Fork 27
Open
Description
1. cmrc2019
- dataset = load_dataset("cmrc2019")
- task_type: cloze-multiple-choice

- example:
load_dataset("gaokao2018_np1", "cloze-multiple-choice")
2. dureader_yesno
- should
answerbeanswers? - we should introduce
contextas a column - this is not a
qa_extractive? it should be qa_multiple_choice or qa_bool?
@register_task(TaskType.qa_bool_dureader)
@dataclass
class QuestionAnsweringBoolDureader(QuestionAnswering):
task: TaskType = TaskType.qa_bool_dureader
question_column: str = "question"
context_column: str = "documents"
answers_column: str = "answers"
answers: {"text": "xxx", "yesno_answer":"Yes"}
3. dureader_search
- the task is
qa_extractivewhile the context_column = "documents" is not a string
4. ckbqa
- this dataset could be broken down to two tasks
- qa_open_domain: question_column, answers_column
- text_to_sql: question_column, sql_column
5. coqa
- Similar to the above one
6. dureader_robust
- the [answers:text, start] () should be sequence, here is one example
"answers": {
answers = {"text": answer_text, "answer_start": answer_start}
(1) answers = [{"text": answer_text, "answer_start": answer_start}]
(2) answers = {"text": [answer_text], "answer_start": [answer_start]}
7. ccpm
- it seems that we can re-use the task
QuestionAnsweringMultipleChoiceWithoutContextfor this dataset
8. cail2019
- Similar to the above one
ccks2019_fin
- the event type should also be regarded as one input?
ccks2020_fin_ee
- rethink if 'event_column' is the best name.
ccks2021_fin_ea
- it seems that the schema of
argumentsis different from the above one, so we probably need to modify the task name a little bit - v.s 2020: define a new task schema for
ccks2021_fin_ea?
ccks2021_fin_re
- it seems that the schema of relation is pretty complicated, should we modify the task name of
event_relation_extraction
Metadata
Metadata
Assignees
Labels
No labels