Your RAG pipeline answers everything correctly. Except anything from a table. Pricing data. Comparison charts. Structured specs. Ask about any of these and the answer is either wrong or completely made up. The model isn't hallucinating because it's bad. It's hallucinating because it never saw the full table. When you chunk documents, you split them by a fixed token count. The splitter doesn't understand what it's cutting through. It just counts and splits. So your pricing table gets sliced in the middle. Half the rows in one chunk, half in another. The model receives an incomplete table and fills in the blanks on its own. Same thing happens with code blocks and any structured content. The moment you start treating tables and code as protected blocks and never let the chunker split through them, the accuracy on structured questions jumps. Same documents. Same model. Same prompt. Just keep structured content whole. I wrote a free playbook (its on git, no email wall or anything) that covers this decision framework (and 6 others like model selection, evaluation, and production optimization) as simple find-your-situation, follow-the-row tables. Link in the first comment.