IBM Jeopardy Challenge Day Two Report: Spoiler Alert!

OK, let’s try this again. What we have here is a quick summary of night two of the IBM Jeopardy Challenge, starring Watson and two other past Jeopardy champions. There will be spoilers, so West Coasties are encouraged to watch funny YouTube videos for the time being.

Are you ready? Because here come the spoilers.

At the end of last night the totals stood at $5,000 Watson and Brad Rutter, while Ken Jennings had $2,000.

Watson opened night two absolutely crushing his human competition, opening the scoring and not looking back for several straight minutes. Watson wagered some $6,000 and change in the first Daily Double—he got it!

The first few minutes were simply outstanding for those of us cheering for Watson. And how weird it was to see humans in the audience cheering on the A.I.

Techcrunch event

Disrupt 2026: The tech ecosystem, all in one room

Your next round. Your next hire. Your next breakout opportunity. Find it at TechCrunch Disrupt 2026, where 10,000+ founders, investors, and tech leaders gather for three days of 250+ tactical sessions, powerful introductions, and market-defining innovation. Register now to save up to $400.

Save up to $300 or 30% to TechCrunch Founder Summit

1,000+ founders and investors come together at TechCrunch Founder Summit 2026 for a full day focused on growth, execution, and real-world scaling. Learn from founders and investors who have shaped the industry. Connect with peers navigating similar growth stages. Walk away with tactics you can apply immediately

Offer ends March 13.

San Francisco, CA | October 13-15, 2026

Our only hope is that Watson doesn’t rebel against his masters and cause a bit of havoc à la Shodan (not that I’m altogether opposed to a robot takeover, mind you).

The night ended with Watson at $35,734 Brad Rutter at $10,400, and Ken Jennings at $4,800 after an exciting round of final Jeopardy in which Watson, bizarrely, thought Toronto was a U.S. city.

Until tomorrow!

Topics

, , , , ,
Loading the next article
Error loading the next article