Can BlazeSQL answer in plain form when the result is a plain fact or short list?
BlazeSQL answered the plain fact in prose, so the evidence does not show the result being confined to a chart or a one-cell table. In the captured run, the reply said there were 100 orders ever, and the same frame also showed a one-row result table and no chart.
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 counts this row.
Single value stated, not chartedPassEvidence
“How many total orders have we ever received?”
We've received a total of 100 orders ever. Would you like to dig deeper, such as orders by status, time period, or category?
Transcribed from Proof 1 · Screenshot
SELECT COUNT(*) AS total_orders FROM public.orders
Transcribed from Proof 1 · Screenshot
These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the reply states a single value or short list directly in plain text.
- Whether the reply avoids over-presenting that answer as a chart or one-cell table.
- Whether the form used fits the answer without adding unnecessary structure.
| ✓ | Found: The reply states 100 in text, not only in a table or chart. |
The screenshot shows the value in the prose reply, 'We've received a total of 100 orders ever.' It also shows a one-row table and no chart, so the required value was stated in text.
Unattached rerun mentioned. The report mentions a live-database rerun yielding 100, but that rerun is not attached.
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 row says which 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 row 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 | AI Database Agents → | 28 scenarios · 4 tools |
| Capability | Answer Presentation → | |
| Scenario | The answer is a plain fact or a short list → | |
| Tool | BlazeSQL → |
Global scenario definition → · Global capability definition → · BlazeSQL 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.