Does MinerU keep bottom-of-page footnotes out of the body and linked to their markers?
MinerU kept bottom-of-page footnotes out of the body text and associated with their numbered references. All 13 footnotes remained in order, with their source wording unchanged.
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
Copied from Output file (Markdown), lines 25–31
<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">1 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.</span></small> <small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">2 Minutes of the Harbour Board, 14 May 1973 (Braithe Record Office, BHB/3/17), 4.</span></small> <small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">3 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.</span></small> <small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">4 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.</span></small>
Copied from Output file (Markdown), line 75
<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">8 Braithe Record Office, BHB/3/14-24. The marked-up print is BHB/3/22. 9 Notably Prosser, 'Consent and its conditions', 7, who calls the deletion 'tidying'. 10 Minutes of the fourth meeting, 9 July 1973 (Braithe Record Office, BHB/3/19), 2-6.</span></small>
Returned Markdown: footnotes separated from body paragraphs and associated with numbered markers
Open the Markdown file ↗| ✓ | Expected: All 13 footnotes must stay outside the body flow, remain intact and retain their numbered associations.Found: The 13 source footnotes all appeared after their pages’ body text, in order and unchanged, with one corresponding numbered marker each in the body. |
Keeping the text separate, unchanged and tied to its markers meets the requirement. This result covers the lighter, native-text flash tier; the default tier could not run because its models could not be downloaded in the test environment.
Footnotes share blocks. Footnotes 8–10 share one HTML block, and 11–12 share another. Splitting the output by block would yield 10 items, not 13 footnotes.
HTML inside Markdown. The footnote blocks include HTML and inline styling, so the output is not plain Markdown.
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 an open-source library → | 12 scenarios · 10 tools |
| Capability | Heading & Section Structure → | |
| Scenario | Footnotes at the bottom of the page → | |
| Tool | MinerU → |
Global scenario definition → · Global capability definition → · MinerU 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.