Browse › Natural Language Processing › Question Answering › SQuAD2.0 dev
SQuAD2.0 dev Benchmark (Question Answering)
Question answering can be segmented into domain-specific tasks like community question answering and knowledge-base question answering. Popular benchmark datasets for evaluation question answering systems include SQuAD, HotPotQA, bAbI, TriviaQA, WikiQA, and many others. Models for question answering are typically evaluated on metrics like EM and F1. Some recent top performing models are T5 and XLNet.
The archive carries no text for this table; the description above is the archive's text for the task Question Answering. archive 2025-07-28
Over time archive 2025-07-28
The chart needs JavaScript; the table below carries every value.
Direction inferred from the metric name, not from the archive: F1 (higher is better). Not inferred (points only, no best-so-far line): EM. Points are placed at the row's paper date; 13 of 13 rows carry one.
Results archive 2025-07-28
Archive rows end at the archive snapshot, 2025-07-28: no result published after that date is in this table. Rank is the archive's row order at that snapshot; not re-ranked here. Metric values are the archive's strings. Column headers sort the table in your browser; each row keeps its archive rank.
| Paper | Code | Ran Syntology | Report | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | XLNet (single model) | 90.6 | 87.9 | – | Paper | Code | 2019 | 10 of 24 ran · 14 unverified | report |
| 2 | XLNet+DSC | 89.51 | 87.65 | – | Paper | Code | 2019 | 0 of 3 ran · 3 unverified | report |
| 3 | RoBERTa (no data aug) | 89.4 | 86.5 | ✓ | Paper | Code | 2019 | 22 of 48 ran · 26 unverified | report |
| 4 | ALBERT xxlarge | 88.1 | 85.1 | – | Paper | Code | 2019 | 46 of 126 ran · 80 unverified | report |
| 5 | SG-Net | 87.9 | 85.1 | – | Paper | Code | 2019 | linked, not harvested | report |
| 6 | SpanBERT | 86.8 | – | Paper | Code | 2019 | 3 of 15 ran · 12 unverified | report | |
| 7 | ALBERT xlarge | 85.9 | 83.1 | – | Paper | Code | 2019 | 46 of 126 ran · 80 unverified | report |
| 8 | SemBERT large | 83.6 | 80.9 | – | Paper | Code | 2019 | 4 of 12 ran · 8 unverified | report |
| 9 | ALBERT large | 82.1 | 79.0 | – | Paper | Code | 2019 | 46 of 126 ran · 80 unverified | report |
| 10 | ALBERT base | 79.1 | 76.1 | – | Paper | Code | 2019 | 46 of 126 ran · 80 unverified | report |
| 11 | RMR + ELMo (Model-III) | 74.8 | 72.3 | – | Paper | – | 2018 | no code linked | report |
| 12 | U-Net | 74.0 | 70.3 | – | Paper | Code | 2018 | linked, not harvested | report |
| 13 | TinyBERT-6 67M | 73.4 | 69.9 | – | Paper | Code | 2019 | 0 of 4 ran · 4 unverified | report |
All 13 rows shown. 13 link to a paper page on this site; 1 are marked as using additional training data in the archive. No GitHub stars are tracked; "Code" is the first repository the archive lists for the row. The archive carries no row tags, review links or community-submitted rows for this table; none are shown. archive 2025-07-28
Syntology Ran reads "N of M ran · U unverified": of the M code samples Syntology harvested from repositories linked to that row's paper (joined by arXiv id), N executed on a synthesized input and the other U = M−N are unverified (harvested, no recorded run). It counts code from repositories linked to that row's paper, not this result: the row's number was not reproduced and nothing here is a correctness claim. The other cell texts mean no graph line for the row: "linked, not harvested" (the archive links code, Syntology has not harvested it), "no code linked" (no code link in the archive), "not matched" (the row's paper URL matched no paper on this site). 10 rows have a graph line, from 7 distinct papers; 8 rows (5 papers) have at least one sample that ran. Counting each paper once: Syntology ran 85 of 232 samples; 147 unverified. Separately, 56 of those 232 are pointer-only (licence): the site points at that code rather than redistributing it, a licence property recorded for ran and unverified samples alike; each cell's tooltip carries the row's own pointer-only count. Read from the graph 2026-09-24. Per-sample status is on the paper page.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections