ModelRefs / Multi-Document Question Answering — AI Glossary

Multi-Document Question Answering — AI Glossary

A task requiring a model to synthesize information from multiple documents to answer a question, testing cross-document reasoning. Also called multi-doc QA.

Overview

Multi-document QA (HotpotQA, 2WikiMultiHop, MuSiQue) requires identifying relevant passages across documents, resolving coreferences, and synthesizing multi-hop reasoning chains. LLMs with long context can use context stuffing; RAG pipelines retrieve relevant documents. Benchmark for testing retrieval quality and reasoning depth.

Reference details

Topicprompting
Also known asmulti-doc QA
Last reviewed2026-06-24

How it works

  1. The question is decomposed, explicitly or implicitly, because the answer does not exist in any single passage.
  2. Candidate passages are gathered from several documents — by retrieval, or by placing all of them in a long context window.
  3. Entities are reconciled across sources, since the same referent appears under different names and a pronoun in one document may resolve only in another.
  4. Facts are composed in order: an intermediate answer from one document conditions what must be found in the next, which is what makes it multi-hop rather than multi-source.
  5. The answer is emitted with attribution per claim, because a synthesised answer that cannot be traced to its sources cannot be checked.

Example: Why the second hop is where retrieval fails

A question needs two facts: the author of a paper, then that author's institution. The first retrieval succeeds — the query terms match the paper's document. The second cannot, because the institution appears in a biography page sharing no terms with the original question; the query needed is the author's name, which was not known until the first hop returned. Single-shot retrieval over the original question therefore has no path to the answer however good the ranking, and this is the structural reason iterative retrieval exists.

Commonly confused with

Collapsed into RAG, which is a method rather than the task. RAG is one way to attempt multi-document QA, and long-context stuffing is another — put every document in the prompt and let attention do the work. They fail differently: retrieval misses the second hop when the query cannot be formed in advance, while stuffing degrades as relevant facts sit further apart in a long context. It is also not the same as single-document QA at larger scale: the defining difficulty is composing facts that no one passage contains, not finding a passage.

When to use it

Reach for it when:

  • Evaluating whether a retrieval pipeline can answer questions requiring more than one source.
  • Explaining why a system that answers single-fact lookups well fails on comparative or chained questions.
  • Deciding between iterative retrieval and long-context stuffing for a corpus.

Reach for something else when:

  • Questions answerable from one passage, however long the document.
  • Summarisation over many documents, where nothing has to be composed to produce the output.

Continue your research

Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Multi-Document Question Answering — AI Glossary.

Frequently asked questions

What is Multi-Document Question Answering?

A task requiring a model to synthesize information from multiple documents to answer a question, testing cross-document reasoning.

Is Multi-Document Question Answering the same as multi-doc QA?

Yes — multi-doc QA are common aliases for Multi-Document Question Answering.

What concepts are related to Multi-Document Question Answering?

Closely related concepts include needle in haystack, open domain qa, rag.