SQuAD (2016) › Limitations
History of Language AIAll chapters SQuAD (2016) › LimitationsOne section · Sections in this chapter5 / 7 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
Despite its wide adoption, SQuAD had several important limitations that shaped subsequent research directions. Perhaps the most significant limitation was that SQuAD questions were created by annotators who had access to the passage when writing questions. This meant that questions were designed to be answerable from the passage, creating a somewhat artificial scenario where the passage was guaranteed to contain the answer. In real-world question answering, users often ask questions that cannot be answered from a given passage, and systems need to recognize when they don't have sufficient information.
The span-based answer format, while enabling clear evaluation, also had limitations. Real questions often require synthesized answers that combine information from multiple parts of a passage or that express the answer in different words than appear in the source text. SQuAD's requirement that answers be exact text spans from the passage meant that systems didn't need to generate or synthesize answers, just identify relevant spans. This made the task somewhat easier than truly open-ended question answering would be.
SQuAD version 1.1 also had some annotation inconsistencies and ambiguities. Some questions had multiple valid answers that appeared in different parts of the passage, but only one answer was marked as correct. Other questions could reasonably be interpreted in multiple ways, leading to potential evaluation issues. The exact match criterion was particularly strict and could penalize systems that identified semantically correct answers but with slightly different span boundaries.
The dataset's focus on Wikipedia articles, while providing diversity, also meant that the passages and questions had certain characteristics that might not generalize to other domains. Wikipedia articles tend to be well-structured, factual, and relatively formal. Questions about Wikipedia passages might not fully test a system's ability to handle more informal text, domain-specific terminology, or narrative passages with complex temporal relationships.
Another limitation was that SQuAD measured reading comprehension ability but didn't necessarily measure deeper reasoning capabilities. A system might successfully extract answer spans by learning sophisticated matching patterns without truly understanding cause-and-effect relationships, logical implications, or complex inferences. The dataset included some questions requiring inference, but many questions could be answered through relatively straightforward information extraction.
The evaluation metrics, while standardized, also had limitations. The exact match metric was binary and strict. This provided no partial credit for answers that were semantically correct but not exact matches. The F1 metric provided some partial credit but still focused on token-level overlap rather than semantic equivalence. Neither metric fully captured whether a system truly understood the question and passage or just learned effective matching strategies.
The single-passage format of SQuAD also limited the types of reasoning it could test. Real reading comprehension often requires integrating information across multiple documents or passages, making connections between different sources, or reasoning about information that isn't contained in a single passage. SQuAD's focus on single-passage question answering couldn't evaluate these multi-document reasoning capabilities.