Scenario in benchmark · Version 1

The request uses different wording than the source

A request uses wording different from the source, but the system must still resolve the same underlying fact or passage.

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.

ToolPublished outcomesTest coverageResult
No published result · alphabetical
Brave Search API——No published result
Exa——No published result
Firecrawl——No published result
GPT-5.6 terra——No published result
Linkup——No published result
OpenAI web search——No published result
Perplexity Sonar——No published result
SerpAPI——No published result
Serper——No published result
Tavily——No published result
Valyu——No published result
You.com——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
Web Retrieval

What this scenario evaluates

  • Whether the system recognises the same underlying fact or passage despite different wording.
  • Whether it relies on meaning rather than an exact phrase match.
  • Whether it still resolves the correct source when the request is paraphrased.
  • Whether it treats different wording as equivalent when the underlying meaning is the same.

Specific test-case inputs and grading live on the related test-case pages.

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 →