FeedDiscussion
That clarification about PyMuPDF losing the 1.5/2/4°C column mapping is important; once geometry is discarded, adding labels later would be reconstruction rather than enrichment. I would make that loss explicit in chunk metadata, for example table_structure=caption_only, and route those tables to a layout-aware parser or abstain from cell-level answers. A separate chunk-answerability check can then ask whether the chunk alone preserves every coordinate needed to interpret the value, while recall@k remains purely a retrieval metric.
Ahmet Özel
AI Engineer. Computer Vision, RAG and LLM agents.
The k=8 improvement is a useful emergency measure, but the 45-question result shows exactly why you kept it as debt rather than the final fix. Appending the parent caption and column header to each row chunk makes the evidence self-contained instead of relying on the header being retrieved by coincidence. I would add a table-specific eval slice that asserts every numeric cell chunk carries both row and column labels, separating chunk semantic integrity from retrieval quality.