How does LiteParse represent a document's data chart in Markdown?
LiteParse did not keep the chart as an image in Markdown. It preserved the chart's title and position, but the output reduced the chart to a placeholder link, with no image file written and OCR text standing in for the chart content.
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.
Data chart — preserved with titleFailEvidence
Change is reported as a mean annual rate over each winter, taken across the whole intertidal part of the line. Accretion varied markedly between transects, and the pattern is the same in each of the three winters measured.  Mean sediment accretion by transect, winters 2023/24 to 2025/26
Markdown output: placeholder chart link, title, and OCR text
Copied from Output file (Markdown), lines 37–41
Open the Markdown file ↗(mm/yr) Accretion 2023/24 2024/25 2025/26 Transect 1 Transect 2 Transect 3 Transect 4 Transect
Copied from Output file (Markdown), lines 43–51
| ✗ | Expected: Keep the chart as an image in place with its title; any added text is optional enrichment.Found: The title and position remain, but the chart becomes a placeholder link with no image file, and OCR text replaces the chart contents. |
It fails because the chart was required as an image with its title, but the output kept only the title and position, plus a placeholder link with no image file behind it. The default pipeline produced OCR text instead of the image.
Loose OCR text. The chart labels appear as loose lines rather than a table, and no chart numbers are invented.
Other figure linked. The page-2 figure is also reduced to a placeholder link, with no file written.
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 | Figures & Charts → | |
| Scenario | A document with a data chart → | |
| Tool | LiteParse → |
Global scenario definition → · Global capability definition → · LiteParse 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.