Enterprise Document Intelligence [Vol. 1 #6a] - Why a user question deserves the same parsing as the document, and how it splits into a retrieval brief and a generation brief before either runs The post RAG Questions Need Parsing Too: Turn the User’s String Into Briefs for Retrieval and Generation appeared first on Towards Data Science .
By angela shi
Enterprise Document Intelligence [Vol. 1 #6quater] - Question parsing takes one messy string and writes four typed pieces, each read by a different downstream call The post Context Engineering for RAG Question Parsing: From a Raw Question to Typed Fields That Steer Retrieval and Generation appeared first on Towards Data Science .
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #6b] - The five field families the parser reads straight from the user’s question, with the code that fills each one The post What the Question Parser Extracts from a User String: Keywords, Scope, Shape, Decomposition, Clarification appeared first on Towards Data Science .
By angela shi
Enterprise Document Intelligence [Vol. 1 #6quinquies] - Prompt engineering, then context engineering, then loop engineering.
By Kezhan 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
The article discusses how an FAQ can invert the traditional Retrieval-Augmented Generation (RAG) pipeline. It explains that parsing becomes trivial, retrieval functions as a cache, and few‑shot prompting is reframed as a retrieval problem. The piece highlights the practical implications of designing a corpus around an FAQ structure for enterprise document intelligence.
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #7ter] - Six positions on the retrieval brick that contradict the cosine-first reflex of mainstream RAG The post The Untaught Lessons of RAG Retrieval: Cosine Is Not the Foundation appeared first on Towards Data Science .
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #9A] - Same paper, same question as Article 1.
By angela shi
The article argues that Retrieval-Augmented Generation (RAG) is only one tool in NLP, and many real-world problems—such as request classification, free‑text matching, table reading, and OCR noise cleaning—are better served by simpler, cheaper techniques. It emphasizes the importance of selecting the appropriate method for each task and highlights the engineering challenge of knowing which technique to apply.
By Kezhan Shi
Enterprise Document Intelligence [Vol. 1 #6bis] - Ask one focused clarification, learn the default from the answer, stay silent next time The post When RAG Users Ask Vague Questions: Clarify Once, Learn the Default appeared first on Towards Data Science .
By angela shi
Enterprise Document Intelligence [Vol. 1 #6c] - The decisions the parser makes on top of the user string, using the document’s profile: dispatch, activations, full schema, three approaches to deciding what fires, the audit _meta block, and a broker-corpus walkthrough The post Dispatching the Parsed RAG Question: Chunk Strategy, Model Tier, Activations, Audit appeared first on Towards Data Science .
By angela shi
Enterprise Document Intelligence [Vol. 1 #8B] - A fixed BASE, the rules each question needs, one registry: the dispatcher that turns a parsed question into a typed LLM call The post Assemble Each RAG Generation Prompt from a Base Prompt Plus the Rules Each Question Needs appeared first on Towards Data Science .
By Kezhan Shi