Enterprise Document Intelligence [Vol. 1 #7quater] - A 492-page document has a 358-entry table of contents.
Enterprise Document Intelligence [Vol. 1 #8bis] - Two regimes for sending retrieved candidates to the generation brick, the sufficiency signal that picks between them, and the per-question type dispatch that makes it cheap The post Loop Engineering for RAG Generation: Iterate top-k One at a Time appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #7B] - Retrieval is filtering on structured tables: keywords first, TOC second, embeddings last The post Anchor Detection for RAG: Parallel Detectors, Then One LLM Call at the End appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #7B] - Retrieval is filtering on structured tables: keywords first, TOC second, embeddings last The post Finding the right anchors for RAG: keyword, embedding, and TOC signals in parallel appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #12] - The category of question most RAG pipelines silently fail on, and the pipeline shape that handles them The post Loop Engineering for Listing Questions: When the Answer Is Every Passage, Not the Top One appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #11] - When the first answer points elsewhere in the document, the pipeline loops back to fetch the linked context The post Loop Engineering for Cross-References: When RAG Answers ‘see Section 7.
The article discusses a method for handling a folder of unrelated PDFs as a single long document with a nested outline. It highlights that without shared fields, an index cannot be built, so the approach uses one summary line per file and each file’s own table of contents, with retrieval routes extending down two levels. This structure enables retrieval-augmented generation (RAG) across multiple documents.
Enterprise Document Intelligence [Vol. 1 #6quinquies] - Prompt engineering, then context engineering, then loop engineering.
Enterprise Document Intelligence [Vol. 1 #7sexies] - The unit of retrieval doesn’t have to be a page or a paragraph.
Enterprise Document Intelligence [Vol. 1 #5octies] - Rules propose, LLM validates: six deterministic signals on span-level typography surface heading candidates, one bounded loop keeps the real ones, and the same toc_df drops back into the RAG pipeline The post Building Document Structure with Loop Engineering: Recovering a PDF’s Outline from Body Typography for RAG appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #13bis] - The four bricks return useful results most of the time.
Enterprise Document Intelligence [Vol. 1 #5septies] - When a PDF prints a contents page but exposes no outline, two ways to turn it back into structure, plus the page-alignment step everyone forgets The post Reconstructing the Table of Contents a PDF Forgot to Ship, So RAG Can Scope by Section appeared first on Towards Data Science .
arXiv:2608. 15064v1 Announce Type: new Abstract: Parsing visual documents into machine-readable representations is fundamental to document intelligence.