Scenario in benchmark · Version 1
Retrieval is scoped to part of the documents
When retrieval is limited to a defined subset of documents, it should stay inside that scope.
How the tools performed
Every in-scope tool is visible. Outcomes come from current published Results for this scenario and benchmark version.
No published results for this scenario yet.
No published result does not tell you whether a tool has been tested. Test coverage is shown only for comparable published Results.
| Tool | Published outcomes | Test coverage | Result |
|---|---|---|---|
| No published result · alphabetical | |||
| Denser AI | — | — | No published result |
| Dify | — | — | No published result |
| FutureSmart Document Intelligence | — | — | No published result |
| Llama Cloud | — | — | No published result |
| Onyx | — | — | No published result |
| Vectara | — | — | No published result |
| Vectorize.io | — | — | No published result |
Assessed = Pass + Fail + Not gradable. Gradable = Pass + Fail. Both use the published Result’s pinned-test denominator. — means not publicly available.
Test design
- Pinned test cases
- 1
- Disclosure
- 0 public · 1 withheld
- Capabilities exercised here
- Retrieval
What this scenario evaluates
- Whether returned results stay within the allowed subset when search is restricted.
- Whether the answer-bearing document outside the allowed subset is excluded from retrieval.
- Whether the system treats a narrow scope as a true no-result case rather than a successful hit.
- Whether the restriction is respected instead of being silently ignored.
Exact wording, inputs, fixture state, expected output and detailed grading remain at the test-case level and may be withheld while the benchmark version is active. The scenario and its evaluation intent are public.
How the results are graded
- Pass: the test-case expectations hold.
- Fail: an expectation demonstrably does not hold.
- Not gradable: the evidence cannot establish the outcome.
Version 1 uses test-case expectations; no scenario rubric is pinned.
Benchmark methodology →