A team evaluates two extractive QA models on a SQuAD-style dataset. Model A achieves an exact match (EM) of 68% and an F1 score of 81%. Model B achieves an EM of 72% and an F1 score of 74%. Which conclusion is most defensible when reporting these results?
- AModel B is strictly superior because its exact match score is higher on the held-out test set.
- BThe two metrics capture different aspects of answer quality, so the preferred model depends on whether partial credit is acceptable in the target application. Correct
- CModel A is strictly superior because its F1 score is higher on the held-out test set.
- DThe evaluation is invalid because SQuAD-style metrics cannot compare extractive models that differ in architecture.
Why A is wrong: Tempting because exact match is the stricter metric and Model B leads there. Wrong because EM penalises any token mismatch, so a model that recovers most of the answer but misses a stop-word scores zero; Model A's higher F1 shows it retrieves more answer tokens on average, making the trade-off non-trivial.
Why B is correct: Exact match requires the predicted span to match the reference exactly, while F1 measures token-level overlap and awards partial credit. Choosing between them is an application decision: high-stakes retrieval may require exact match; conversational assistants may tolerate partial matches. Reporting both and contextualising the trade-off is the defensible approach.
Why C is wrong: Tempting because F1 is often cited as the primary SQuAD metric and Model A leads there. Wrong because neither metric dominates in all use cases; the right choice depends on whether partial credit matters to the application, so a one-dimensional superiority claim based on a single metric is unjustified.
Why D is wrong: Tempting because architectural differences can affect comparability in some evaluation frameworks. Wrong because SQuAD EM and F1 are output-level metrics applied to predicted answer spans regardless of model architecture; they are specifically designed to compare any extractive QA system on a shared held-out benchmark.