NovelQA: Benchmarking Question Answering on Documents Exceeding 200K Tokens
Overview
NovelQA: Benchmarking Question Answering on Documents Exceeding 200K Tokens is an academic paper released in March 2024 on arXiv (https://arxiv.org/abs/2403.12766). The work was authored by Cunxiang Wang, Ruoxi Ning, Boqi Pan, Tonghui Wu, Qipeng Guo, Cheng Deng, and 5 other collaborators.
Motivation
Most question answering benchmarks are built on short passages of a few hundred tokens, which fails to reflect the real-world demand for systems that can read, index, and reason over entire documents such as books, legal contracts, or technical reports. NovelQA addresses this gap by constructing a QA benchmark where each question is anchored in a full-length novel exceeding 200K tokens.
What the Benchmark Tests
- Long-range understanding: questions require integrating information spread across distant chapters.
- Multi-hop reasoning: answers depend on combining clues from multiple locations in the text.
- Context window vs. retrieval: the benchmark enables comparison between long-context LLMs (reading the whole novel at once) and retrieval-augmented or agentic pipelines (iteratively retrieving relevant passages).
- Evaluation of Retrieval-Augmented Generation: A Survey (arXiv:2405.07437)
- ARES: An Automated Evaluation Framework for RAG (arXiv:2311.09476)
- A Dataset of Information-Seeking Questions and Answers Anchored in Research Abstracts (arXiv:2105.03011)
- AgentBoard: An Analytical Evaluation Board of Multi-turn LLM Agents (arXiv:2401.13148)
Positioning in the Field
This entry belongs to the Evaluation of Search Engines section of the forum's awesome list. It fits along the "retrieval → ranking → generation/agentic → evaluation" chain alongside related resources:
Takeaways for Practitioners
1. Researchers: use NovelQA to stress-test long-context models against retrieval-based baselines; verify statistical significance and compute costs when citing results. 2. Engineers: benchmark pluggable components (retrievers, rerankers, planners) on document-scale QA before integration; pay attention to p99 latency budgets and index update strategies. 3. Product teams: user-perceivable quality on long documents (answer faithfulness, citation accuracy) matters more than passage-level nDCG improvements.
Caveats
This post summarizes the benchmark based on its abstract and public metadata. Quantitative results should be verified against the original PDF before citation. Note that novel-centric English benchmarks may not generalize across languages or document genres (e.g., enterprise or multimodal documents).