A RAG pipeline retrieves context from a knowledge base of long policy PDFs. Users report answers that miss clauses spanning page boundaries. Which indexing change is most appropriate?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — if a requirement straddles two chunks, tiny non-overlapping slices will hide half the sentence. Overlap or hierarchical chunking keeps the clause together for retrieval.
Full explanation below image
Full Explanation
Boundary-spanning content is a classic RAG failure mode. Overlapping chunks or parent-child hierarchical indexing preserves local context so retrieval can return complete clauses. Single-word chunks destroy semantics. Filename search ignores body text. Screenshot storage loses structured retrieval. Teams should evaluate chunk size, overlap, and metadata filters against a golden question set.