Does LlamaParse keep footnotes out of the body flow and attach them to their references?
LlamaParse kept all 13 footnotes out of the body text and tied each one to its reference. Each page's notes come after that page's body, every note on its own line, and every reference mark in the body is a superscript that matches a note, with every note matching a mark.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Footnote — out of body flow, associatedPassEvidence
We sent the complete four-page PDF to LlamaParse's parse API in one request, with every setting left at its default.
Returned Markdown: superscript marks in the body, each page's notes below it
Copied from Output file (Markdown), lines 23–29
<sup>1</sup> Braithe Estuary Order 1974, art. 6(2). The Order is reproduced in full in the appendix to R. Sandiman, *The Braithe Estuary: A Documentary History* (Vardenne, 1988), 211-24. <sup>2</sup> Minutes of the Harbour Board, 14 May 1973 (Braithe Record Office, BHB/3/17), 4. <sup>3</sup> The point was not argued in *Tarbert v Braithe Harbour Board* [1981] 2 EstLR 88, where both parties proceeded on the assumption that art. 6(2) applied. <sup>4</sup> The Board's file on the 2011 consents (Braithe Record Office, BHB/11/4) contains three letters returned undelivered and a note of a telephone call to a solicitor in Winnipeg.
API response: the completed job and all four pages processed
Copied from Captured file (JSON), job › status
COMPLETED
| ✓ | Expected: The footnote text is present, kept out of the body text, and tied to the reference mark that points to it.Found: All 13 notes are present, grouped on their own lines below their own page's body, and each matches a superscript mark earlier in the body, in both directions. |
- job › tier
- agentic
- job › name
- croyde_1974_braithe_order_offprint.pdf
The notes had to be present, kept out of the body text, and tied to their references. All three held: all 13 notes appear, each below its own page's body and never inside a paragraph, and all 13 marks and notes match each other.
Running heads kept as lines. The running heads and page numbers of the source pages are kept, each on its own line at a page boundary, and none is spliced into a sentence or a note.
Run-together marks separated. Where the source's text runs a note mark into the word before it, after 'willing to consent' and 'the position of tenants', the output keeps each mark as its own superscript; no body word differs.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Converting a complex PDF into clean Markdown with a hosted API → | 12 scenarios · 13 tools |
| Capability | Heading & Section Structure → | |
| Scenario | Footnotes at the bottom of the page → | |
| Tool | LlamaParse → |
Global scenario definition → · Global capability definition → · LlamaParse product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.