Keep page references attached during extraction, before passages are merged or chunked. Reconstructing page numbers afterward can produce convincing citations that point users to the wrong evidence.
Page provenance needs explicit conventions
A PDF has physical page positions and may display different printed page labels. A cover and front matter can shift those relationships. The retrieval system should distinguish its internal page index from the page label users see.
For a proposed span model, retain source identity and version, physical page reference, printed label where supported and verified, and relevant geometry or text span. A chunk spanning pages should preserve all contributing locations rather than keep one arbitrary number.
Do not infer a printed page label solely by adding a constant offset. Appendices, restarts, missing labels, and inserted pages can invalidate that shortcut.
Test a fictional policy manual
The PDF begins with a cover and two unnumbered pages, then starts printed page one. A relevant paragraph begins on one page and its exception continues on the next. The citation should help a user locate both pieces under the interface’s stated convention.
A later source revision inserts another page before the section. Existing answer evidence must still identify the original version or be re-evaluated. Silently opening the latest page at the old position can misrepresent historical support.
| Provenance case | Required behaviour |
|---|---|
| Cover and front matter | Internal position distinguished from printed label |
| Passage crosses pages | All relevant locations preserved |
| OCR-derived region | Source page and region retained |
| Revised PDF | Version relationship explicit |
| Missing printed label | Honest physical-page convention |
Use labelled fictional pages and ask reviewers to locate the exact evidence from generated citations. A citation string passing format validation does not prove that it points to the supporting passage.
Preserve provenance through transformations
Extraction, layout repair, deduplication, chunking, and context assembly should carry source relationships forward. If two passages merge, keep their distinct locations and do not fabricate one continuous source range.
Detailed geometry increases metadata and storage. Page-level references may suffice for simple documents, while dense tables or multi-column pages benefit from finer locations. Choose the detail needed for actual verification and keep source permission checks on citation opening.
This provenance design is proposed. The ChalkLens case study documents source-based classroom workflows without claiming these citation controls. Pair it with answer-to-passage tracing.
Page reference FAQ
Is page zero the first printed page?
Not necessarily. State the internal convention and distinguish any visible printed label.
Can one page number describe a cross-page chunk?
Preserve the relevant contributing locations instead of implying all evidence sits on one page.
What should a citation test prove?
An authorised user can locate the actual supporting content in the correct source version using the displayed reference.