Does Landing AI keep footnotes out of the body flow and attach them to their references?
Landing AI kept footnotes outside body paragraphs while preserving their references. It retained all thirteen notes intact, grouping each page’s notes after its body text.
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 submitted the complete four-page journal offprint to Landing AI’s document-to-Markdown conversion API in one request, without model or options overrides.
Copied from Output file (Markdown), lines 56–62
<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.
Copied from Output file (Markdown), lines 130–207
5 Report of the Committee on Estuarine Consents (Cmnd 6712, 1977), paras 88-94. 6 See further A. Prosser, 'Consent and its conditions' (1994) 12 EPR 3, 9-14, whose account of the 1977 committee differs from mine at one point of substance. 7 The Harbour Board series appears to have been reconstructed in 1981, probably for the purposes of the Tarbert litigation. <!-- PAGE BREAK --> THE 1974 BRAITHE ORDER AND THE LIMITS OF CONSENT 145 The committee's papers are in two series and neither is complete. What survives of the drafting is a bundle of eleven documents: four memoranda, the minutes of six meetings, and a marked-up print of the draft Order with two hands on it, one of them the secretary's.<sup>8</sup> The sequence that matters begins at the second meeting, on 14 May 1973, at which the solicitor's memorandum was considered and not adopted. The minute is short and gives no reason, which has led more than one writer to treat the decision as a formality.<sup>9</sup> The marked-up print shows that it was not. The words 'the owner for the time being' are struck through in the secretary's hand, and beside them, in the other hand, is written 'not without the tenancy point'. That note is the hinge of this article. It ties the deletion to the tenancy question, which the committee took up at its fourth meeting and settled in a way that makes the wider reading of article 6(2) impossible. The connection appears not to have been noticed before, and the tenancy discussion is worth setting out at length.<sup>10</sup> The problem the committee faced was this. Much of the foreshore between the training wall and Thrimby Point was let, in 1973 as now, on grazing tenancies of a year and less. If consent ran with the land, a consent given by an owner would bind a tenant who had not been asked; if it did not, the Board would have to seek consent from whoever held the land at the date of the works, tenant or owner. The committee wanted neither result and said so in terms. 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. <!-- PAGE BREAK --> 146 HELENA M. CROYDE Its solution was article 6(3), which nobody reads: consent is required from 'the owner and, where the land is let for a term of more than one year, the tenant'. The threshold of a year is the committee's own and appears nowhere else in the Order.<sup>11</sup> Article 6(3) only makes sense on the narrow reading. If consent ran with the land, a tenant's consent would run with the tenancy, and a threshold of a year would protect nobody: a grazing tenant of eleven months would be bound by a consent given by a predecessor's landlord, which is precisely the result the committee said it wished to avoid. On the narrow reading the threshold does what the minute says it was for. There is a further point, smaller but harder to answer. The committee considered and rejected a draft in which consent was expressed to bind 'successors in title'. The rejected words are in the same marked-up print, struck through in the same hand.<sup>12</sup> A committee that struck out 'the owner for the time being' and 'successors in title' at consecutive meetings was not tidying. The remainder of the drafting history adds little. The Order was settled at the sixth meeting and went to the department unchanged in this respect. The department's own file, which I have not seen, is said to contain nothing on article 6 at all.<sup>13</sup> 11 Braithe Estuary Order 1974, art. 6(3). The threshold is discussed at the fourth meeting, ibid., 5. 12 Braithe Record Office, BHB/3/22, fo. 4. 13 I am grateful to the departmental records officer for a search, and for the confirmation that the file was weeded in 1998.
Copied from Output file (JSON), metadata
{ "job_id": "parse-01m22n0gk374he0ezb30eyazw1", "model_version": "dpt-3-pro-20260710", "page_count": 4, "output_markdown_chars": 11053, "range_units": "unicode_codepoints", "openapi_spec": "https://api.ade.landing.ai/openapi.json", "failed_pages": [], "duration_ms": 21403, "billing": { "service_tier": "priority", "total_credits": 9.6 } }
Returned Markdown: separate footnote blocks and inline reference markers
Open the Markdown file ↗Raw API response: converted text and processing details
Open the whole JSON file ↗| ✓ | Expected: Keep all thirteen footnotes intact, outside body paragraphs and associated with the sentences that reference them.Found: All thirteen notes remain intact in separate blocks after each page’s body; thirteen inline reference markers remain attached to their sentences. |
Separate note blocks and sentence-level references meet the required structure. Note 4 is present through the end of its sentence, so its text is complete rather than truncated.
Inconsistent note numbering style. Notes 1–4 use superscript numbers at the start of the note; notes 5–13 use plain leading numbers.
Running heads remain. The returned Markdown keeps the running heads and printed page numbers on their own lines.
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 | Landing AI → |
Global scenario definition → · Global capability definition → · Landing AI 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.