Does Upstage AI turn styled headings into nested Markdown heading levels?
Upstage AI returned every heading of the three-page procedure at a single Markdown level, so the source's three heading sizes collapsed into one and no nesting survived. Three headings, including Refrigerated storage, came back as plain lines with no heading marker.
1 of 1 test case failed
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.
Styled headings — hierarchy preservedFailEvidence
We sent the complete three-page PDF to Upstage's document conversion endpoint in one request, with every setting left at its default; nothing was typed.
Copied from Output file (Markdown), lines 3–37
# Sample Reception and Handling Procedure KAL-SP-06 · Revision 4 · Effective 1 March 2026 # Scope This procedure covers the receipt, identification, storage and disposal of samples submitted to the laboratory for chemical analysis. It applies to everything received at the Braithe Road reception, including samples delivered by courier and samples brought in by clients. It does not cover samples taken by our own field staff, which are dealt with in KAL-SP-11. # Reception Samples are received at reception between 08:00 and 17:30 on weekdays and between 09:00 and 12:00 on Saturdays. Outside those hours clients who hold a key may use the refrigerated drop box at the rear entrance. # Chain of custody Every delivery arrives with a completed submission form. Reception staff check that the form is signed, that the number of containers matches the number listed on it, and that each container carries a legible client reference. The form is signed and timed on receipt and the top copy is returned to the person making the delivery. # Condition on arrival Reception staff record the condition of each container on the submission form before it leaves the reception bench. Anything recorded there that falls outside the limits below goes to the duty chemist before the sample is booked in. # Temperature Chilled samples. Where the submission form specifies chilled transport, the temperature of the transport box is measured and written on the form. A box above 8 degrees is accepted, marked, and referred to the duty chemist, who decides whether the analysis can still be reported. A box above 15 degrees is not accepted for microbiological work at all. # Container integrity
Copied from Output file (Markdown), lines 42–55
# Storage Refrigerated storage Samples for chemical analysis are held at 4 degrees in the reception cold room and are racked by the day of receipt, not by client. Racks are cleared every Friday afternoon. # Frozen storage Samples that require frozen storage are held at minus 20 degrees in the chest freezer in room 4. Nothing goes into the freezer without a completed freezer label, and nothing is stacked above the load line marked inside the cabinet. Retention and disposal
Copied from Output file (Markdown), lines 83–85
Identification and booking in # The laboratory number
Returned Markdown: every heading at one level, three source headings as plain text
Open the Markdown file ↗| ✗ | Expected: Headings come back as Markdown headings with their levels and nesting kept, not as plain or bold text.Found: The source's 26 headings use three sizes (16, 13, 12 point); every returned heading is one '#' level, and three headings, such as Refrigerated storage, are plain lines. |
The test required headings to become Markdown headings with their nesting kept. The source sets headings at three sizes above the body text; the returned Markdown uses one heading level for all of them, and three headings carry no marker at all, so both parts of the requirement fail.
Body-size title made a heading. The title line "Sample Reception and Handling", set at body size in the source, came back as a top-level heading.
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 | A document with styled headings and subheadings → | |
| Tool | Upstage AI → |
Global scenario definition → · Global capability definition → · Upstage 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.