Enterprise Document Intelligence [Vol. 1 #9B] - One call wires the four upgraded bricks together, run on a paper, a NIST standard, and a report with a broken TOC The post A Production RAG Pipeline in Action: Every Answer Typed and Cited appeared first on Towards Data Science .
By angela shi
Enterprise Document Intelligence [Vol. 1 #9A] - Same paper, same question as Article 1.
By angela shi
Enterprise Document Intelligence [Vol. 1 #4bis] - A coauthor note on the brick-by-brick pitfalls that justified the four-brick split, before Part II walks the fixes The post 10 Common RAG Mistakes We Keep Seeing in Production appeared first on Towards Data Science .
By Kezhan Shi
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.
By angela shi
Enterprise Document Intelligence [Vol. 1 #1] The smallest version of RAG that actually works, on a real PDF, with grounded answers and the source lines highlighted.
By angela shi
The article discusses the importance of a Retrieval-Augmented Generation (RAG) system providing clear evidence when it states that information is not present in a document. It outlines four distinct types of evidence that should accompany such a claim to avoid presenting a confident but incorrect answer or an unsupported “no answer.” The piece emphasizes that each evidence type serves as a safeguard against misinformation in enterprise document intelligence.
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #5A] - Document signals (metadata, native TOC, source software) and page-level content (text vs scans, tables, images, columns, page profile) The post Beyond extract_text: The Two Layers of a PDF That Drive RAG Quality appeared first on Towards Data Science .
By Kezhan Shi
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.
By angela shi
The article explains that enterprise document intelligence can be categorized into three distinct corpus types, each requiring a specific architecture. It outlines how to determine the shape of a document collection through three key questions. The piece also discusses the costs associated with building a system for the incorrect corpus type.
By angela shi
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 .
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #5B] - One PDF in, a relational set of DataFrames out: lines, pages, TOC, images, cross-references, captions, spans, and a parsing summary The post Stop Returning Flat Text from a PDF: The Relational Tables RAG Needs appeared first on Towards Data Science .
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #5B] - One PDF in, a relational set of DataFrames out: lines, pages, TOC, images, cross-references, captions, spans, and a parsing summary The post Stop Returning Flat Text from a PDF: The Relational Shape RAG Needs appeared first on Towards Data Science .
By Kezhan Shi