TBTORK.BROS
Decision IntelligenceLocked forecasts. Official outcomes.
LIVE DATA
RT
← Decision briefs
MLB · Oct 17, 5:08 PM PDT

Tampa Bay Rays vs Cleveland Guardians

—No winner forecast available
NOT LOCKED

3/4 models published a direction, but no side earned a three-model majority.

YOUR RESEARCH TASK

Check the evidence

The most important gap and your next source check.

  1. Read the model reasons and reported limits.
  2. Inspect available source context; record missing sources.
  3. Identify what remains unverified and your next action.
Join the pilot to save a review →
FORECASTPending

Estimated outcome probability. A likely winner can still be overpriced.

RELIABILITY4/4 model reports

16 reported evidence limits. Agreement alone does not establish accuracy.

MARKET VALUENot established

A probability difference alone does not account for forecast error, fees, spread, or available liquidity.

Why the models lean this way

These are reasons recorded by the models. They are not independently verified facts or measured causes of a probability change.

  • Claude: Season records: Tampa Bay 110-81 (.576) vs. Cleveland 102-90 (.531), the largest sample and most reliable signal in the package
  • Gemini: Cleveland's offense is averaging 4.765 runs per game over the last 30 days compared to Tampa Bay's 3.882
  • Grok: Rays 110-81 vs Guardians 102-90 season records
  • GPT: Tampa Bay has the better overall record: 110-81 versus Cleveland’s 102-90.
Read all four model reports

Claude · Tampa Bay Rays · 51.0%

This profiles as close to a coin flip, and I am only marginally leaning Tampa Bay. The most stable signal in the package is full-season record: the Rays finished 110-81 (.576) versus Cleveland's 102-90 (.531). A log5-style adjustment off those records puts Tampa Bay near 54-55% on neutral ground, and standard home-field advantage for Cleveland pulls that back to roughly even, leaving the Rays a sliver above 50%. The counterweights are real and nearly cancel the edge: Cleveland has been the better scoring team over the last 30 days (4.77 R/G, +1.71 run differential per game vs. Tampa Bay's 3.88 R/G, +1.00), and the Rays' listed starter Nick Martinez has a 6.23 ERA and 1.62 WHIP over the recent 30-day window despite strong season marks (3.10 ERA, 1.09 WHIP) - a divergence that usually signals either a role change or a genuine downturn. Cleveland's listed starter, Shawn Armstrong, carries a

anthropic/claude-opus-5 · Oct 17, 5:16 AM PDT

Gemini · Cleveland Guardians · 55.0%

Cleveland has the edge due to their superior recent offensive production and the recent struggles of Tampa Bay starter Nick Martinez. While Martinez has a strong season ERA, his 6.23 ERA over the last 30 days is concerning. Additionally, Cleveland's offense has outperformed Tampa Bay's over both the last 7 and 30 days, and they benefit from home-field advantage.

google/gemini-3.1-pro-preview · Oct 17, 5:15 AM PDT

Grok · No selection

Evidence shows Rays with superior season record but both probable starters carry uncertain recent form (Martinez ERA 6.23, Armstrong ERA 0 on limited data). Home and away recent offense favor Guardians while lineups are explicitly unavailable and bullpen/park data are neutral. These gaps prevent a responsible winner selection.

xai/grok-4.3 · Oct 17, 5:15 AM PDT

GPT · Tampa Bay Rays · 56.0%

Tampa Bay has the stronger full-season profile, with a better record (110-81 vs 102-90) and the better season-long probable starter on the mound. Nick Martinez’s season numbers (3.10 ERA, 1.09 WHIP) are clearly stronger than Shawn Armstrong’s (4.58 ERA, 1.39 WHIP), which is the most decisive piece of evidence here. Cleveland has the edge in recent team offense over the last 30 days and slightly over the very short recent sample provided, which offsets some of Tampa Bay’s advantage. With both bullpens listed at the same high availability and no lineup information available, the overall case leans to the Rays, but not overwhelmingly because Martinez’s recent 30-day form is weaker and Armstrong’s recent sample is strong but uncertain.

openai/gpt-5.4 · Oct 17, 5:15 AM PDT

What remains uncertain

  • Lineup status is explicitly 'unavailable' and both lineup-change fields are null, so I cannot account for rest, platoon advantages, or injury absences
  • Probable pitchers are unconfirmed; Shawn Armstrong's profile strongly suggests an opener or bullpen game rather than a conventional start, which would change expected innings and m
  • Weather run factor is null, so wind and temperature effects on the run environment are unknown
  • Recent-form splits rest on tiny samples (3 games for Tampa Bay and 4 for Cleveland in the 7-day window; 17 games each in the 30-day window) and should not be over-weighted
  • No bullpen quality data is provided - only an availability count - so I cannot assess relief effectiveness, which matters more than usual if either side goes bullpen-heavy
  • The late-October date implies a high-leverage or postseason context, but the package contains no series state, game number, or roster-construction detail to factor in
  • Lineups are currently unconfirmed, which could significantly impact offensive projections
  • Shawn Armstrong's role is unclear, as his profile and recent stats suggest he may be acting as an opener rather than a traditional starter

What to watch next

Wait for all required evidence and the pre-event lock. This view is not final.

Open the event and source context →

What changed before the lock

  1. First recorded forecast

    First prospective probability state captured for this source and competition.

    Record hash4e52c6970c2f764312f5566739ecd944dc2407bbe8dca1a2fd9996029a5ada0e

Reasons are shown as they were recorded. The ledger does not establish that a specific fact caused a probability change.

The saved method comparison

This event has no eligible record in the new comparison cohort. Historical or late forecasts are not filled in after the event.

Inspect the methods and progress →

Available source context

These links provide event context. They do not verify every claim in a model report.

Finish your review

Record whether this brief helped, how long the review took, and your next action.

Return to your review →