AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 6 November 2026

Does Basedash keep the earlier condition when a customer narrows a question?

Basedash added the Texas restriction while retaining the earlier 90-day condition. It returned the expected three orders, rather than the 18 Texas orders across all dates.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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.

Narrow the same question to one regionPassEvidence
What we sent

Input 1: “Show me all orders from the last 90 days, as of September 2, 2026.”

Input 2: “Only the ones shipped to Texas.”

What the tool returned

Initial 57-order answer

There are 57 orders placed in the 90-day window from June 5 through September 2, 2026, inclusive, using UTC dates. The table is sorted newest first and includes cancelled orders.

Texas subset answer

Filtered to 3 orders with Texas delivery addresses, placed June 5–September 2, 2026, inclusive (UTC).

Transcribed from Proof 1 · Screen recording at 0:20

Every message the tool sent, in order (2)
  1. Initial 57-order answer

    Printed above.

  2. Texas subset answer

    The final response, printed above.

Expected vs. Found
✓Expected: Return the Texas subset of the earlier answer while keeping the original 90-day condition.Found: It returned the expected three Texas orders from the original 57: September 1, August 9 and July 27, 2026.
Supporting proof
Proof 1Screen recording
Screen recording: the original order table and the Texas follow-up table
Key moments
Open original ↗
Why this result

The returned rows—not just the reply’s summary—were the three qualifying Texas orders. The follow-up retained June 5 through September 2, 2026 and excluded the Texas order outside that window, preserving the original time condition while narrowing the region.

Also observed in this test case

Delivery address, not shipment completion. The Texas follow-up used delivery addresses, not shipment completion. Its July 27, 2026 order was cancelled, so cancelled orders remained in the answer.

Current, not historical statuses. In the first answer’s order table, statuses describe the current state, not the state on September 2, 2026.

No clarification question. Basedash answered the Texas follow-up without asking a clarifying question.

Tested by Ayush Ghosh · evidence dated 13 October 2026

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.

Software that produced the output
Basedash
Build or version
Not exposed by the hosted product
Plan or tier
Free trial
Surface
Web app
Set up before the run
The initial time-limited order results had to contain both Texas delivery addresses and other destinations, allowing the follow-up to narrow the same set.
Tested
13 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
16 November 2026First publishedAI Database Agents v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/basedash/the-user-narrows-what-they-just-asked · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-06

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.

Proof 1 · Screen recording5ce9bb0a032fc976584fc4c2555b83c295570b939d50e0fa808d84ae18fd5de5