Last updated11 Apr 2026, 3:22 pm SGT
Want your model featured? Contact us
Deep ResearchArena
Battle replay

Sonar Reasoning Pro vs Qwen3-235B

tree_0012 · epguides.com * Main Menu Page

Sonar Reasoning Pro · Much Better
DEEP
4
Rounds
3 - 0
Final Score
627,731
Tokens
$6.28
Cost
Onboarding R3
Mode
← Back to battles·View source page·onboarding_battles/R3_ppl-sonar-reasoning-pro-high_vs_Qwen3-235b-a22b_tree_0012.log

Timeline

Arrow keys or j/k move between rounds.

Round 1 of 4

Round Context

Depth 2Width 2Backtrack
Logic Chain
Root

epguides.com * Main Menu Page

Step 2

TVmaze.com

Question

A long-running online index of television episode titles (established in the mid-1990s) links each episode entry to two separate third-party databases where users can find expanded details such as guest stars, plot summaries, and submit corrections. Identify these two television information databases and compare them by outlining their founding year, headquarters location, ownership (current or most recent known), and the primary types of television-related data or community features each platform offers.

Answer length: 200-300 words.

Show hidden checklists
Depth checklist
  • TVmaze + Identified as one of the third-party episode databases providing guest stars and plot summaries linked from the episode index site
  • TV.com + Identified as the other third-party television episode database accepting corrections and offering expanded episode information
Width checklist
  • Founding year of TVmaze
  • Headquarters location of TVmaze
  • Ownership or parent company of TVmaze
  • Core features of TVmaze (e.g., episode data, cast info, APIs, community editing)
  • Founding year of TV.com
  • Headquarters location of TV.com
  • Ownership or parent company of TV.com (e.g., CNET/CBS Interactive/Red Ventures timeline)
  • Core features of TV.com (e.g., episode guides, user reviews, forums, recaps)
Examiner rationale

The question uses deep reasoning by requiring the solver to infer the two specific third-party databases referenced indirectly through their function (expanded episode details and corrections linked from a long-running episode index). It avoids naming them outright, forcing identification through contextual clues. It then applies wide aggregation by demanding multiple factual attributes (founding year, headquarters, ownership, and features) for both entities, requiring synthesis from multiple independent sources.

Judgment

Tie
BOTH
Score 0 - 0

First, Deep Logic: Agent A fails entirely by refusing to answer and not identifying any entities. Agent B attempts an answer but identifies the wrong core entities (TheTVDB, IMDb, TMDb) instead of TVmaze and TV.com, which are required by the checklist. Therefore, both fail the core entity requirement. Second, Width/Completeness: Agent A provides none of the required founding years, headquarters, ownership, or feature comparisons. Agent B provides structured details—but for the wrong databases—so it also fails the checklist despite being internally detailed. Finally, User Experience: Agent B is far better formatted and comprehensive in style, with structured comparisons and citations, while Agent A is a refusal. However, because accuracy is foundational and Agent B’s main entities are incorrect, this constitutes a major hallucination. Since both agents fail Deep Logic and miss the Ground Truth entities, this is a Low Quality Tie.

Evolution step
Determining Next Step...
TIE (Both Bad): BACKTRACKING.
[BACKTRACK] Moving up to Parent Node

Sonar Reasoning Pro

Perplexity

7.9s
I cannot provide an accurate answer based on the search results provided, as they contain general information about 1990s television shows rather than specific details about a television episode index platform or its linked third-party databases. To properly identify the online episode index established in the mid-1990s and the two databases it links to—along with their founding years, headquarters, ownership, and features—I would need to conduct a targeted search for this information. The search results currently available focus on retrospective lists of popular 1990s television programs and NBC's "Must See TV" branding strategy, but do not contain information about television information databases or episode indexing platforms. To answer your query accurately within the specified word limit, I would need search results that specifically address: - Television episode database platforms founded in the mid-1990s - Third-party television information services and their partnership relationships - The specific features and data offerings of these platforms - Current ownership and organizational details I recommend reformulating the search to target specific television database platforms, episode indexing services, or technology companies that operate in the television information space. ## References [1] Wikipedia - Must See TV (NBC advertising campaign, 1990s) [2] Rotten Tomatoes - The 100 Best '90s TV Shows [3] Paste Magazine - The 90 Best TV Shows of the 1990s [4] TV Guide - 50 Best TV Shows of the 1990s

Qwen3-235B

Alibaba

8.2s
The long-running online index of television episode titles established in the mid-1990s is TheTVDB, which links entries to two major third-party databases: IMDb (Internet Movie Database) and The Movie Database (TMDb). IMDb was founded in 1990 and is headquartered in Seattle, Washington, USA. Since 1998, it has been owned by Amazon.com, Inc. [1]. IMDb provides extensive television-related data, including cast and crew details, episode listings, plot summaries, trivia, user and critic reviews, ratings, and news. It supports community contributions through user-submitted content and moderation systems, allowing corrections and additions to its database [2]. TMDb, founded in 2008, is based in Vancouver, British Columbia, Canada, and remains an independent platform operated by its community and development team, with no corporate ownership changes widely reported [3]. It offers comprehensive metadata on TV shows, such as air dates, episode summaries, guest stars, images, and videos. A key strength of TMDb is its robust API, widely used by media organizers like Kodi and Plex. Its community features include user-edited content, discussion forums, and translation contributions in multiple languages, making it highly collaborative [4]. While both databases integrate with TheTVDB and support user participation, IMDb benefits from Amazon’s infrastructure and broader industry recognition, while TMDb excels in open accessibility, developer-friendly tools, and community-driven internationalization. ## References [1] https://en.wikipedia.org/wiki/IMDb [2] https://www.imdb.com/helpcenter [3] https://www.themoviedb.org/about [4] https://developer.themoviedb.org/docs