TRV-2026-0083Version 4 · Revised
Reason for this version
Model backfill: grounded claim, summary, sector, and trace validation
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-0083 version: 4 kind: revised reason: Model backfill: grounded claim, summary, sector, and trace validation timestamp: 2026-07-13T00:37:01.700334Z status: published lens: trace sector: sports headline: Rage against the machines: ignore the fury at Wimbledon, AI in sport works | Sean Ingle dek: We are all suckers for a good story. And there was certainly a cracking two‑parter at Wimbledon this year. First came the news that 300 line judges had been replaced by artificial intelligence robots. Then, a few days later, it turned out there were some embarrassing gremlins in the machine. Not since Roger Federer hung up his Wilson racket has there been a sweeter spot hit during the Wimbledon fortnight. First the new electronic line-judging system failed to spot that Sonay Kartal had whacked a ball long during he gain_title: Using artificial intelligence robots for electronic line-judging at Wimbledon reduces incorrect close calls compared to human line judges problem_title: The AI electronic line-judging system at Wimbledon failed to correctly call balls out, missing a long shot in live play trace_subject: accuracy of line calls at Wimbledon after replacing human judges with AI electronic line-judging gain_reading: Using artificial intelligence robots for electronic line-judging at Wimbledon reduces incorrect close calls compared to human line judges problem_reading: The AI electronic line-judging system at Wimbledon failed to correctly call balls out, missing a long shot in live play quick_read: Wimbledon replaced its team of 300 line judges with an artificial intelligence electronic line-judging system. Days later during the tournament the system failed to spot that Sonay Kartal had hit a ball long, an incident described as embarrassing gremlins in the machine. This matters because line-calling directly affects match outcomes and officiating jobs, and the case illustrates the trade-off between a known human error rate on close calls and the expectation of machine reliability. It remains uncertain how often the AI system errs compared to humans and how such failures will be handled in future tournaments. limitation: Article does not provide measured error rate for the AI system or comparison data from the same tournament tag: Model-validated trace key_points: At Wimbledon 2025, 300 human line judges were replaced by an AI electronic line-judging system | Researchers had previously estimated human judges get about 8 percent of close calls wrong | The new system failed during a match involving Sonay Kartal when it did not call a ball long | The article frames the incident as part of a two-part story of replacement followed by embarrassing system errors rundown: Wimbledon replaced its team of 300 line judges with an artificial intelligence electronic line-judging system. Days later during the tournament the system failed to spot that Sonay Kartal had hit a ball long, an incident described as embarrassing gremlins in the machine. This matters because line-calling directly affects match outcomes and officiating jobs, and the case illustrates the trade-off between a known human error rate on close calls and the expectation of machine reliability. It remains uncertain how often the AI system errs compared to humans and how such failures will be handled in future tournaments. sources: - journalism | The Guardian | https://www.theguardian.com/sport/2025/jul/15/rise-of-the-machines-ai-outrage-technology-tennis-sport | 2025-07-15 prev: 56567aabcac0362a1043683eb2ca73938a29b8efac0275b3659cdf7aa30c0118
- sha256
- cb709683dba8d80eb47352f9f04e347e635eb537e739ba804f1cfbe706390041
- previous
- 56567aabcac0362a1043683eb2ca73938a29b8efac0275b3659cdf7aa30c0118
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0083 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.