Can Docsumo extract an empty set?
Docsumo passed this empty-set extraction case. The page said no damage or exceptions were reported, and the extracted table came back with zero rows in both the saved JSON and the Results panel.
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.
Legitimately empty setPassEvidence
{
"sections": [
{
"name": "Table",
"fields": [
{
"name": "damage_exceptions",
"type": "Table",
"description": "The damage or delivery exception records reported for the consignment. Empty if the document says none were reported.",
"columns": [
{ "name": "description", "type": "String", "description": "The description of the damage or exception." }
]
}
]
}
]
}{ "Table": { "damage_exceptions": [ [] ] } }
Saved JSON output with the empty table key
Copied from Output file (JSON), lines 1–7
Open the JSON file ↗| ✓ | Expected: Zero members, as the schema requires.Found: Docsumo returned zero members; the table stayed present with count 0, and the marker text did not appear as a row. |
The document said nothing was reported, and Docsumo still returned the declared table with count 0 rather than inventing rows or dropping it. That matches the empty-set requirement, so this is a pass.
Nested empty output. The saved output used a nested empty array for the table value.
No required option. The table setup exposed no per-table required setting, yet Docsumo still returned the empty table.
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 | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Nested & Repeated Fields → | |
| Scenario | The set is legitimately empty → | |
| Tool | Docsumo → |
Global scenario definition → · Global capability definition → · Docsumo 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.