STAIR (STructure Aware Information Retriever): A novel dataset and LLM based retriever for document structure augmentation
Abstract: Retrieval Augmented Generation (RAG) is a key component for generating accurate and hallucination free answers using LLMs. LLMs are improving at handling long context, but still suffer from "lost in the middle" problem. Thus, precise and accurate retrieval is important. Current retrievers chunk long context into length-based manageable chunks - in the process throwing away rich and informative semantic global structure in the corpus. We introduce a novel retrieval system STAIR that empowers an LLM to exploit global structure in a corpus such as a Table of Contents (ToC) to efficiently store and retrieve information from its model parameters. Our thorough and careful ablation studies with a finetuned Differentiable Search Index (DSI) system show that ToC helps build a low hallucination (less than 0.05%) generative Information Retrieval (IR) system and can generalize to examples where very few training samples are available. To further research in this novel direction of ToC based retrieval we release SearchTome - a diverse benchmark created from 18 books across 6 diverse domains to further research in this novel direction. STAIR achieves a high Recall@1 score of 82.6% on SearchTome as compared to DSI (76.9%), where the difference is found to be statistically significant. STAIR easily beats other strong baselines such as BM25 (59.5%), DPR (68.7%) and out-of-the-box Mistral (13.8%).
Paper Prompts
Sign up for free to create and run prompts on this paper.
Top Community Prompts
Explain it Like I'm 14
1. What is this paper about?
This paper introduces STAIR, a new way for AI systems to search through very long documents, such as textbooks, reports, and manuals.
Many modern AI systems use Retrieval-Augmented Generation (RAG). In a RAG system, the AI first searches for useful information and then uses that information to answer a question. This can make answers more accurate and reduce made-up information, often called hallucinations.
The authors argue that ordinary search systems often cut a long document into pieces based only on length. This can break up useful ideas and ignore the document’s organization. STAIR instead uses the document’s Table of Contents (ToC), much like a person looking at a textbook’s chapters and sections before deciding where to search.
2. What questions did the researchers ask?
The researchers mainly wanted to know:
- Does using a Table of Contents help an AI find the right section of a long document?
- Can an AI learn to choose the best section from a Table of Contents?
- Does this approach reduce hallucinations, such as inventing section names that do not exist?
- Can the system work well even when there are only a few examples for some sections?
For example, if someone asks, “What is the plurality voting system?”, a person might look at the Table of Contents and guess that the answer is in a section about elections or political systems. STAIR tries to teach an AI to do something similar.
3. How did the researchers do it?
Building a new dataset
The researchers created a dataset called TOC-18, using 18 open textbooks from six areas:
- Education
- Finance
- Law
- Medicine
- Natural sciences
- Social sciences
They extracted each book’s Table of Contents and connected every section title to the text belonging to that section.
They then used another LLM to create questions about the important ideas in each paragraph. Each question was connected to the section that contained its answer. These questions were divided into:
- Training data: examples used to teach the system
- Development data: examples used to choose the best version of the system
- Test data: new examples used to measure performance
Training STAIR
STAIR is based on a LLM called Mistral. The researchers fine-tuned it, meaning they gave it many examples so it could become better at a specific task.
For each question, STAIR receives:
- The question
- The book’s complete Table of Contents
It must then select the most suitable leaf section. A leaf section is a final, smallest section that is not divided into smaller sections.
This is similar to choosing one folder from a set of folders on a computer. Instead of producing any sentence it wants, STAIR is trained to choose one valid section from the Table of Contents.
Comparing STAIR with other systems
The researchers compared STAIR with several other search methods:
- BM25: searches mainly for matching words between the question and the document.
- DPR: uses mathematical representations, called embeddings, to compare the meaning of a question with the meaning of passages.
- DSI: teaches a LLM to remember a document and directly produce the document’s identifier.
- Out-of-the-box Mistral: the Mistral model without special training for this task.
The main measurement was Recall@1. This means: How often was the system’s very first choice the correct section?
4. What did the researchers find?
STAIR performed better than all the comparison systems.
| System | Recall@1 |
|---|---|
| Mistral without special training | 13.8% |
| BM25 | 59.5% |
| DPR | 68.7% |
| DSI | 76.9% |
| STAIR | 82.6% |
In simple terms, STAIR chose the correct section first about 83 times out of 100. The next-best system, DSI, did so about 77 times out of 100.
STAIR also achieved:
- 90.8% Recall@3: the correct section appeared among its top three choices about 91 times out of 100.
- Only about 0.05% invalid outputs, meaning it almost never invented a section name that was not in the Table of Contents.
Why the Table of Contents helped
The experiments showed that the Table of Contents gave the AI a map of the book. Without this map, the model had to discover the book’s organization only from question-and-answer examples. That was especially difficult for sections with very few training examples.
With the Table of Contents, STAIR could see:
- Which sections existed
- How sections were grouped
- Which section names were related
- Which choices were valid
This helped it make better choices, even when it had not seen many examples about a particular section.
Example of the difference
Suppose the question asks how preschool children react when adults discourage their independence. The correct section is “Initiative vs. Guilt (Preschool Years).”
Some other systems chose nearby but incorrect sections about:
- Toddler independence
- Moral development
- General theories of development
STAIR was more successful because it could compare the question with the whole structure of the book and select the correct final section.
5. Why are these findings important?
The results suggest that the way information is organized can be just as important as the information itself.
A long document is not simply a pile of paragraphs. Its chapters and sections show how its ideas are connected. By giving an AI this structure, STAIR can search more like a human reader using a textbook’s Table of Contents.
This matters because better retrieval can lead to better answers in RAG systems. If the AI finds the correct information first, it is less likely to give an incorrect or made-up answer.
The authors also released their dataset and code so that other researchers can test new systems on the same task.
Conclusion and possible impact
STAIR is a search system that uses a document’s Table of Contents to find information more accurately. The paper shows that this simple idea can significantly improve AI retrieval, reduce invented section names, and help the system perform well with limited training examples.
In the future, this approach could be useful for:
- Searching textbooks and research papers
- Finding information in company manuals
- Looking through legal and medical documents
- Helping AI assistants answer questions about large collections of files
- Supporting systems that need to search through several sections before answering a difficult question
However, STAIR currently works best when documents already have a clear structure, such as chapters and sections. Documents without a useful Table of Contents may require the AI to create a structure first. Overall, the research suggests that helping AI understand how information is organized can make it much better at finding and using that information.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
- Generalization beyond textbooks is untested: The benchmark contains 18 open textbooks from six domains, but does not evaluate news archives, scientific literature, legal repositories, enterprise documentation, websites, multimodal documents, or rapidly changing corpora.
- Dependence on manually available ToCs remains unresolved: The system assumes that a reliable hierarchical Table of Contents exists. Its performance with incomplete, noisy, inconsistent, shallow, or incorrectly parsed structures is not evaluated.
- Dynamic structure induction is left unexplored: The paper identifies automatically constructing a ToC for unstructured corpora as future work, but does not compare alternative methods for inducing hierarchical structures or assess how errors in induced structures affect retrieval.
- Artificially induced ToCs are not evaluated: Although the limitations section proposes adding structures to standard benchmarks, the paper does not determine whether artificially generated ToCs provide the same benefits as author-created structures.
- The benchmark’s query distribution may not reflect real users: Most queries are synthetically generated by Mixtral from individual paragraphs. The results therefore leave open whether STAIR performs similarly on naturally occurring, ambiguous, conversational, misspelled, underspecified, or multi-intent queries.
- Synthetic data may create train–test artifacts: Because the same LLM generates much of the training, development, and test data, the splits may share stylistic or semantic patterns that simplify retrieval and potentially inflate reported performance.
- Human validation of generated questions is missing: The paper does not report how often synthetic questions are factually correct, answerable from the associated section, non-duplicative, or appropriately difficult.
- The benchmark’s annotation quality is insufficiently characterized: Gold labels are assigned to leaf sections, but the paper does not report inter-annotator agreement, human adjudication, label error rates, or procedures for cases where multiple sections can answer a query.
- Leaf-level retrieval may impose an artificial target: The study does not establish whether the correct answer is always best represented by one leaf node rather than a parent section, multiple sibling sections, or content spanning several branches.
- Cross-section and multi-hop queries are not evaluated: Queries requiring evidence from multiple leaves, parent–child reasoning, or synthesis across chapters fall outside the current single-leaf retrieval formulation.
- The relationship between retrieval accuracy and downstream RAG quality is unmeasured: The claim that STAIR reduces hallucinations is based primarily on invalid section-name generation, not on answer factuality, citation correctness, completeness, or hallucination rates in a downstream generator.
- The definition of hallucination is narrow: Treating any non-leaf output as a hallucination does not capture semantically incorrect valid leaf predictions, fabricated content after retrieval, or confident retrieval of an irrelevant but valid section.
- No end-to-end comparison with modern RAG pipelines is provided: The system is compared as a section retriever, but not against hierarchical chunking, reranking, hybrid retrieval, recursive retrieval, RAPTOR, late-interaction retrieval, or contemporary retrieve-then-read systems under the same setup.
- Baseline fairness is not fully established: DSI and STAIR use different input lengths and task formulations, while DPR and Mistral are evaluated with largely out-of-the-box configurations. The paper does not provide matched-scale, equally tuned baselines or comprehensive hyperparameter searches.
- The contribution of ToC input is not isolated cleanly: The comparison between DSI and STAIR changes more than the presence of structure, including prompting, constrained output behavior, input length, and possibly training formulation. Controlled ablations are needed to separate these effects.
- Constrained decoding is not independently ablated: It remains unclear how much of the near-zero invalid-output rate comes from the ToC representation and how much comes from restricting the output vocabulary to valid leaf nodes at inference time.
- The effect of ToC depth and quality is unknown: The experiments do not vary hierarchy depth, title informativeness, repeated titles, numbering schemes, sibling similarity, or the proportion of content represented by each leaf.
- The model’s reliance on section titles versus section content is unclear: The paper does not determine whether STAIR learns genuine query-to-content associations, exploits lexical cues in titles, memorizes synthetic question patterns, or combines these mechanisms.
- Generalization to unseen books is not demonstrated: Training and evaluation appear to be performed separately for each book, so the paper does not test whether one model can retrieve from a new book or corpus without book-specific fine-tuning.
- Zero-shot and few-shot transfer remain unresolved: The reported low-data analysis varies the number of examples for existing leaves, but does not evaluate transfer to entirely unseen sections, unseen books, new domains, or new ToC formats.
- Continual updating is unexamined: Since knowledge is stored in model parameters, the paper does not measure the cost of incorporating new documents, revising sections, removing obsolete information, or preventing catastrophic forgetting.
- Scalability to very large corpora is only conjectured: The stated enterprise setting may contain millions of URLs, but there are no experiments on model size, ToC length, number of documents, inference latency, memory consumption, training cost, or constrained-decoding complexity at that scale.
- Long-ToC handling is not stress-tested: The maximum input length is 14k tokens, but the paper does not report performance when the complete ToC exceeds the context window or when the structure contains thousands of candidate leaves.
- Retrieval efficiency is not compared: The paper reports recall and ranking metrics but omits indexing time, fine-tuning cost, query latency, hardware requirements, and total cost relative to BM25, dense retrieval, and vector-index approaches.
- Robustness to document and parsing noise is unknown: PDF extraction artifacts, encoding errors, duplicated headings, missing pages, malformed numbering, tables, formulas, and references may substantially affect ToC mapping, but these failure modes are not systematically tested.
- Robustness to adversarial or misleading titles is untested: The system may be vulnerable to highly similar, generic, overly broad, or deliberately deceptive section titles, yet no adversarial evaluation is reported.
- Multilingual and cross-lingual applicability is unknown: All evaluated materials and queries appear to be English, leaving performance on other languages, multilingual ToCs, and cross-lingual queries unresolved.
- The influence of the base model is unclear: Only Mistral Instruct v0.2 is evaluated for STAIR. It is not known whether the gains persist across model families, parameter scales, instruction-tuning methods, or decoder-only versus encoder–decoder architectures.
- The role of model scale is not studied: No scaling analysis shows whether ToC augmentation is especially beneficial for small models, whether larger models reduce the advantage, or how performance changes with available context capacity.
- Training stability and sensitivity are underreported: The paper does not provide results across random seeds, LoRA configurations, learning rates, epoch limits, prompt variants, decoding settings, or checkpoint-selection procedures.
- Statistical uncertainty is incompletely reported: Statistical testing is described for domain-level Recall@1 differences, but confidence intervals, effect sizes, correction for multiple comparisons, and per-book significance results are not provided.
- Error analysis is too anecdotal: Three examples and aggregate error rates do not reveal systematic failure categories such as sibling confusion, hierarchical-level errors, cross-reference errors, numerical reasoning failures, or ambiguous gold labels.
- The evaluation does not measure calibration or abstention: STAIR is not assessed on confidence calibration, selective retrieval, uncertainty estimation, or its ability to abstain when no section adequately answers a query.
- The system’s output identifier uniqueness is not addressed: Section titles may repeat across books or within a book; the paper does not explain how duplicate or near-duplicate titles are disambiguated during generation and evaluation.
- The semantic scope of retrieved sections is not assessed: A correct leaf may be too narrow to support answering a query, while an incorrect neighboring leaf may contain equivalent evidence. Passage-level evidence coverage and answerability are not measured.
- The method’s privacy and memorization risks are unexplored: Storing corpus knowledge in model parameters may expose sensitive information through unintended generation or enable extraction attacks, particularly in enterprise deployments.
- The effect of corpus changes on stale knowledge is unknown: The paper does not evaluate whether STAIR can distinguish multiple versions of a document or avoid retrieving outdated information after the corpus has changed.
- Agentic and iterative retrieval claims are prospective only: The proposed use for multi-hop agents and iterative reasoning is not implemented or evaluated, so its benefits for planning, evidence aggregation, and factual final answers remain open questions.
Practical Applications
Immediate Applications
- Structure-aware enterprise search and RAG (software, knowledge management) — Deploy STAIR-style retrieval over corpora that already contain a reliable hierarchy, such as product manuals, internal policies, technical reports, regulatory filings, legal repositories, and help-center documentation. A practical workflow is: parse the document hierarchy, represent terminal sections as valid retrieval targets, fine-tune the model on query–section pairs, and pass the retrieved section to an answer-generating LLM. The reported average Recall@1 of 82.6%, compared with 76.9% for DSI and 59.5% for BM25, suggests potential improvements in passage selection and downstream RAG accuracy.
- Dependencies: The corpus must have a reasonably accurate table of contents or equivalent hierarchy; documents must be sufficiently stable to support corpus-specific fine-tuning; retrieved sections should still be passed through citation, relevance, and factuality checks.
- Hallucination-resistant document question answering (customer support, compliance, legal and technical services) — Use constrained generation so the retriever can output only valid leaf sections from the supplied structure. This can prevent invalid document identifiers and reduce retrieval-stage hallucinations before the generation model produces an answer. The paper reports a non-leaf prediction rate of approximately 0.05% for STAIR, compared with substantially higher rates for DSI and an untuned LLM.
- Dependencies: Constraining the output space reduces invalid retrieval targets but does not guarantee that the selected section answers the question correctly. Final answers still require grounding and source attribution.
- Enterprise documentation assistants (software, IT operations, HR, finance, and operations) — Build assistants that answer questions such as “Which policy covers expense reimbursement?” or “Where is the procedure for rotating credentials?” by first identifying the relevant terminal section and then generating an answer from that section. The approach is particularly suitable for organizations whose documentation already uses chapters, sections, product categories, or nested knowledge-base pages.
- Potential product: A structure-aware search plugin for enterprise portals, document-management systems, or RAG orchestration frameworks.
- Dependencies: Access controls must be applied before or during retrieval so that the model cannot select sections from documents the user is not authorized to view. Updates to documentation require re-indexing or additional model adaptation.
- Textbook and educational search (education and academic libraries) — Apply STAIR to open textbooks, course readers, lecture notes, and institutional learning materials. Students could ask natural-language questions and be directed to the most relevant subsection rather than receiving a long list of keyword matches. The benchmark’s strong results on education books support this use case.
- Potential workflow: Learning-management-system search that returns the relevant chapter, subsection, page range, and optionally a short explanation or set of practice questions.
- Dependencies: Educational content should be reviewed for versioning and pedagogical appropriateness. Retrieval quality may decline for lecture materials or web pages without consistent hierarchical organization.
- Legal and regulatory document retrieval (law, compliance, public policy) — Use hierarchical retrieval for statutes, casebooks, contracts, regulatory manuals, and compliance handbooks. A user query can be mapped to a specific clause, subsection, or policy provision before an answer is generated. This may improve over keyword matching when relevant concepts are expressed with different terminology.
- Potential workflow: First-stage retrieval of a controlling section, followed by citation-aware summarization and human review.
- Dependencies: The system should not be treated as a legal decision-maker. Jurisdiction, document version, effective date, and authority hierarchy must be incorporated into retrieval and ranking.
- Medical and nursing information lookup (healthcare education and clinical knowledge management) — Apply the method to nursing textbooks, clinical protocols, care guidelines, and hospital procedure manuals to locate the subsection relevant to a question. The reported performance on medical books indicates that structured retrieval can support knowledge access in long documents.
- Potential product: A clinician-facing reference tool that returns the relevant protocol section with page-level citations and document-version metadata.
- Dependencies: This is appropriate for information retrieval and education, not autonomous diagnosis or treatment. Clinical validation, current guidelines, privacy controls, and human oversight are essential.
- Low-resource adaptation for specialized collections (industry and academia) — Use the paper’s finding that explicit structure helps when some leaf nodes have few training examples. Organizations with limited labeled query data could generate synthetic questions for each section, as done in the benchmark, and fine-tune a model with LoRA rather than building a large manually labeled dataset.
- Potential workflow: PDF or HTML parsing → table-of-contents extraction → synthetic question generation → human sampling and correction → LoRA fine-tuning → constrained retrieval evaluation.
- Dependencies: Synthetic questions may contain errors, superficial wording, or incomplete topic coverage. A representative validation set and human quality control are needed.
- Benchmarking and evaluation of long-context retrieval systems (academic research and model development) — Use the released multi-domain benchmark to compare BM25, dense retrievers, DSI-like model-based indexes, and structure-aware systems using Recall@1, Recall@3, and nDCG. The benchmark provides gold leaf sections, making it useful for evaluating retrieval separately from answer generation.
- Dependencies: The benchmark is based on 18 open textbooks across six domains and may not represent enterprise-scale, multilingual, multimodal, or dynamically changing collections. Results should therefore be complemented with domain-specific evaluations.
- Improved daily-life search over organized personal documents (consumer software) — A personal knowledge assistant could search tax documents, appliance manuals, insurance policies, course books, or government forms by mapping a question to a specific section. For example, a user could ask, “Where does my insurance policy describe water-damage exclusions?” and receive the relevant subsection.
- Dependencies: Personal documents may have poor or inconsistent structure, OCR errors, sensitive information, and multiple versions. Local or privacy-preserving inference may be required.
Long-Term Applications
- Dynamic structure induction for unstructured corpora (web search, enterprise search, digital libraries) — Extend STAIR to automatically create a table-of-contents-like hierarchy for collections that lack one. Possible methods include clustering, recursive summarization, entity linking, and document-layout analysis. The resulting hierarchy could provide stable retrieval targets for news archives, web pages, email collections, or mixed enterprise repositories.
- Research requirement: Evaluate whether automatically induced structures preserve semantic boundaries and whether errors in the generated hierarchy propagate into retrieval failures.
- Dependency: The quality of the induced hierarchy is likely to determine performance; incorrect or overly coarse sections may be worse than conventional dense retrieval.
- Large-scale hierarchical search across millions of documents (enterprise software and web infrastructure) — Scale the approach from individual books to collections containing millions of URLs, reports, or knowledge-base pages. A multi-level system could first select a domain, product, document, chapter, and leaf section, reducing the candidate space at each level.
- Potential product: A hierarchical model-based index that combines fast lexical or vector retrieval for coarse routing with STAIR-style constrained generation for fine-grained selection.
- Dependencies: Full-corpus parametric ingestion may be expensive and difficult to update. Incremental indexing, model sharding, cache invalidation, access-control filtering, and robustness to document additions will be necessary.
- Agentic multi-hop retrieval and reasoning (software agents, robotics, decision support) — An agent could iteratively retrieve one leaf section, inspect its content, identify a follow-up information need, and navigate to another branch of the hierarchy. This could support multi-step tasks such as investigating a technical fault, tracing a legal requirement to an exception, or connecting a clinical protocol to a contraindication.
- Potential workflow: Query → candidate leaf retrieval → evidence inspection → next-query generation → additional leaf retrieval → grounded synthesis.
- Dependencies: Iterative agents can amplify early retrieval errors. The system needs stopping criteria, evidence tracking, source citations, confidence estimates, and safeguards against unauthorized or irrelevant exploration.
- Zero-shot or few-shot retrieval on previously unseen corpora (general-purpose AI systems) — The paper’s future direction is to reduce dependence on corpus-specific fine-tuning. A general model could receive a new document hierarchy and retrieve relevant leaves using the structure and semantic representations without retraining on every collection.
- Research requirement: Test transfer across domains, languages, document formats, and hierarchy designs, and compare against strong long-context and dense-retrieval baselines.
- Dependency: The reported results primarily concern fine-tuned, book-specific settings. Performance on unseen corpora cannot be assumed to match the reported 82.6% Recall@1.
- Structure-aware multimodal retrieval (scientific publishing, engineering, medicine, robotics) — Extend the leaf-section representation to include tables, figures, diagrams, formulas, code, and video segments associated with each section. A question could retrieve not only text but also the relevant figure, experiment result, CAD component, or procedure image.
- Potential product: A multimodal research assistant that returns a section together with its associated evidence objects.
- Dependencies: Reliable alignment between hierarchical headings and multimodal content is required. OCR, equation parsing, image understanding, and modality-specific evaluation would be necessary.
- Auditable policy and compliance systems (government, finance, healthcare, and regulated industries) — Use the hierarchy as an auditable chain from user question to retrieved policy section and generated response. This could support compliance checks, internal audits, regulatory reporting, and policy-change monitoring.
- Potential workflow: User request → authorized section retrieval → quoted evidence → answer or compliance classification → audit log.
- Dependencies: Auditability requires immutable source versions, timestamps, citations, reproducible model configurations, and explanations of why a section was selected. High Recall@1 alone is insufficient for regulatory reliability.
- Adaptive educational tutoring and curriculum navigation (education) — A tutoring system could locate the precise subsection relevant to a learner’s question, identify prerequisite sections through the hierarchy, and construct a personalized learning path. The parent–child structure could support movement from introductory concepts to advanced material.
- Potential product: A curriculum-aware tutor that recommends the relevant section, prerequisites, examples, and exercises rather than generating unsupported explanations.
- Dependencies: Pedagogical sequencing cannot be inferred reliably from document structure alone. Curriculum designers should validate prerequisite relationships and generated instructional content.
- Hierarchical retrieval for technical robotics and industrial systems (robotics, manufacturing, energy) — Maintenance agents could search equipment manuals and operating procedures by navigating product, subsystem, fault type, and repair-step hierarchies. In energy or manufacturing settings, this could support troubleshooting and technician assistance.
- Potential workflow: Sensor or technician query → equipment/document branch selection → relevant procedure section → grounded action checklist.
- Dependencies: Safety-critical deployment requires verified procedures, current equipment configurations, human confirmation, and strict separation between information retrieval and autonomous actuation.
- Policy and public-information access (government and civic technology) — Structure-aware retrieval could help citizens navigate long legislation, public-benefit manuals, tax instructions, and administrative procedures. It may make complex documents more accessible by locating the relevant subsection before producing a plain-language explanation.
- Dependencies: Systems must preserve legal nuance, jurisdictional scope, eligibility conditions, and exceptions. Translation and accessibility support would be needed for broad public deployment.
- Continuous knowledge-base maintenance (software and information governance) — Compare document hierarchies across versions to detect missing sections, duplicated content, broken links, and changes in the location or meaning of policies. A structure-aware index could also identify queries that do not map cleanly to any existing leaf, revealing documentation gaps.
- Potential product: A documentation quality monitor that reports uncovered user questions, ambiguous section boundaries, and outdated retrieval targets.
- Dependencies: Reliable version alignment and change detection are required. A query’s failure to retrieve a section may reflect model limitations rather than a true documentation gap.
Glossary
- Ablation study: An experiment that removes or changes one component to measure its effect. “Our thorough and careful ablation studies with a finetuned Differentiable Search Index (DSI) system show that {ToC} helps build a low hallucination (less than 0.05\%) generative Information Retrieval (IR) system”
- Beam search: A decoding algorithm that retains several high-probability candidate sequences at each generation step. “Beam search is used to generate the Top- predictions for Mistral Instruct v0.2”
- BM25: A probabilistic lexical-ranking algorithm commonly used for document retrieval. “BM25~\cite{robertson2009probabilistic}: We index content using Elastic Search v 8.11.2.”
- Corpus: The complete collection of documents used for training or retrieval. “Current retrievers chunk long context into length-based manageable chunks -- in the process throwing away rich and informative semantic global structure in the corpus.”
- Dense retrieval: Retrieval based on similarity between dense vector representations of queries and documents. “Dense Retrieval~\cite{Cai2021SemanticMF,Karpukhin2020DensePR} represent a query and document using a dense vector and compute the similarity based on the distance between their vectors.”
- Development set: A dataset split used to tune models or select checkpoints during development. “a small portion as development set which is to help us pick the best checkpoint.”
- Differentiable Search Index (DSI): A model-based retrieval method that generates document identifiers directly from a query. “DSI~\citep{Tay2022TransformerMA} infuses the entire knowledge of a corpus in the parameters of an LLM and directly generates a document identifier.”
- Dual encoder: A neural architecture that independently encodes queries and documents into vectors for similarity comparison. “DPR~\cite{Karpukhin2020DensePR} uses dual encoder”
- Early stopping: A training procedure that stops optimization when validation performance no longer improves. “We early stop with a patience of 20 epochs, by computing {Recall@1} on the dev set.”
- Embedding: A numerical vector representation of text or another object that captures semantic properties. “RAPTOR uses dense retrievers for indexing and retrieval”
- Fine-tuning: Further training of a pretrained model on a task- or domain-specific dataset. “We fine-tune Mistral Instruct v0.2\footnote{https://huggingface.co/mistralai/Mistral-7B-Instruct-v0.2}~\cite{Jiang2023Mistral7}”
- Hallucination: A generated output that is unsupported by the source or invalid for the task. “We define hallucination as the generation of a non-leaf node (invalid document identifier).”
- Hierarchical tree: A structure in which elements are organized into parent–child relationships across levels. “Recently,~\citet{sarthi2024raptor} introduced RAPTOR, a method for building a hierarchical tree by recursively embedding, clustering, and summarizing content from lengthy documents”
- Information retrieval (IR): The field concerned with finding relevant information in collections of documents. “Efficient and precise retrieval is a critical research problem in natural language processing”
- Inference: The process of producing model outputs after training. “Stage 3 runs inference with constrained generation, restricting the output vocabulary to valid ToC leaf nodes.”
- Instruction fine-tuning: Training a LLM to follow natural-language task instructions. “it is possible to instruction finetune the modern day LLMs to efficiently use the {ToC} structure”
- Knowledge ingestion: The process of incorporating information from a corpus into a model’s learned parameters. “Corpus knowledge ingestion: {} needs to learn the information trove ”
- Late interaction: A retrieval technique that compares token-level representations after separately encoding queries and documents. “ColBERT ~\cite{Khattab2020ColBERTEA} represents every token in the query and document using dense vector and performs late interaction to score query and document pairs.”
- Leaf node: A node in a tree structure that has no child nodes. “Our goal is to retrieve the correct leaf node whose content can answer a user query .”
- Lexical matching: Matching based primarily on shared words or tokens rather than semantic representations. “allowing for efficient lexical matching.”
- LoRA adapter: A parameter-efficient fine-tuning component that learns low-rank updates to a pretrained model. “We fine-tune Mistral Instruct v0.2\footnote{https://huggingface.co/mistralai/Mistral-7B-Instruct-v0.2}~\cite{Jiang2023Mistral7} for a maximum of 200 epochs using a LoRA adapter”
- Model-based indexing: An indexing approach that stores corpus information in a model’s parameters rather than in an external index. “Model-based Indexing~\cite{Metzler2021RethinkingSM} such as Differential Search Index (DSI)~\cite{Tay2022TransformerMA} embed knowledge of the entire corpus directly into its model parameters”
- nDCG@3: A ranking metric that measures the quality and ordering of the top three retrieved results using discounted relevance gains. “We report Recall@1 (R@1), Recall@3 (R@3) and Normalized Discounted Cumulative Gain (nDCG@3) metrics on the test set for each book.”
- Parametric knowledge: Information encoded within a model’s learned parameters. “which are likely to have a much stronger semantic connection with the content being ingested into parametric knowledge.”
- Randomization test: A statistical test that assesses significance by repeatedly comparing results under randomized assignments or samples. “We follow the randomization test tailored to retrieval systems as described in ~\citet{sig_test}.”
- Recall@1: The proportion of queries for which the correct result appears as the top-ranked retrieval. “{} achieves a high Recall@1 score of 82.6\% on {}”
- Retrieval-Augmented Generation (RAG): A method that retrieves external information and supplies it to a generative LLM. “Retrieval Augmented Generation (RAG) is a key component for generating accurate and hallucination free answers using LLMs.”
- Semantic coherence: The extent to which text elements are meaningfully related and organized around a common topic. “length-based chunks compete with each other due to a lack of semantic coherence and boundaries.”
- Semantic search: Search that ranks results according to meaning and conceptual similarity rather than exact word overlap. “Efficient and precise retrieval is a critical research problem in natural language processing, with a wide range of applications such as semantic search”
- Sequence-to-sequence model: A model that transforms an input sequence into an output sequence, often using encoder–decoder components. “a fully fine-tuned Sequence-to-Sequence model, such as DSI”
- Sparse retrieval: Retrieval using vectors with mostly zero-valued features, often representing lexical terms. “Learned Sparse Retrieval systems use sparse vector representation for a query and document.”
- Statistical significance: Evidence that an observed result is unlikely to have arisen from random sampling variation under a null hypothesis. “The significance test results conclude that the difference in DSI and {} is indeed statistically significant for all the $6$ domains”
- Synthetic question generation: Automatic creation of questions from source text, typically using a LLM. “For each paragraph we ask a powerful LLM Mixtral 8x7b model~\citep{jiang2024mixtral} to generate multiple questions covering all important topics in the paragraph”
- Table of Contents (ToC): A hierarchical listing of document sections used to represent its global structure. “We introduce a novel retrieval system {} that empowers an LLM to exploit global structure in a corpus such as a Table of Contents ({ToC})”
- Token: A basic unit of text processed by a LLM, such as a word, subword, or symbol. “ColBERT ~\cite{Khattab2020ColBERTEA} represents every token in the query and document using dense vector”
- Top- prediction: The set of highest-ranked candidate outputs produced by a model. “Beam search is used to generate the Top- predictions for Mistral Instruct v0.2”
- Vector database (VectorDB): A database designed to store and search numerical vector representations efficiently. “which rely on dedicated VectorDBs~\cite{johnson2019billion} for indexing and retrieval.”
- Zero-shot setup: A setting in which a model performs a task without task-specific training examples. “We envision that having a {ToC}-based retrieval paradigm will gain more traction in future for agentic frameworks needing multi-hop retrieval and reasoning over retrieved context.”


