← All posts
Weather·August 25, 2026Council was wrong

The AI council leaned 40% toward 33°C in Kuala Lumpur on August 25 — the high was 32°C

What the market asked

The Polymarket event was straightforward in wording and strict in resolution: what would be the highest temperature in Kuala Lumpur on August 25? Outcomes were framed as whole-degree Celsius buckets. Resolution depended solely on the highest whole-degree value in the Temp column of the NOAA WRH timeseries for station WMKK (Kuala Lumpur International Airport) on the local calendar date 25 August 2026.

That single-station, single-column rule left little room for alternative weather sources or rounding disputes. The question was pure observational weather, not a forecast beauty contest.

What the council concluded

Report date was 2026-08-24, one day before the event. Participating models were Grok, Claude, and GPT, with Grok as chairman. The council’s action was SKIP, with overall confidence at 58%. Its most-likely outcome—and the graded pick—was “Will the highest temperature in Kuala Lumpur be 33°C on August 25?” at 40% probability.

The published reasoning stated:

Council recommends SKIP. Confidence: 58%. Resolution is strictly the highest whole-degree Celsius value appearing in the Temp column of the NOAA WRH timeseries for station WMKK (Kuala Lumpur International Airport) on the calendar date 25 August 2026 (local).

In short, the group recognized the narrow resolution criteria, assigned only moderate confidence, and declined a strong directional bet while still surfacing 33°C as the mode of their distribution at 40%.

How the probabilities sat

Under the grade basis of “most_likely,” the council’s 40% on 33°C was the figure that mattered for scoring. No higher-probability alternative was elevated above it in the report. A 40% top outcome in a multi-bucket temperature market implies a relatively flat distribution: several nearby highs (31°C, 32°C, 34°C, etc.) remained plausible, and the council did not claim sharp conviction. The explicit SKIP recommendation reinforced that view—edge was judged insufficient relative to the resolution risk and day-ahead uncertainty typical of tropical station readings.

What actually happened

The market resolved to 32°C: “Will the highest temperature in Kuala Lumpur be 32°C on August 25?” The council’s graded pick of 33°C was therefore incorrect. council_was_correct is false. The Brier score on the graded most-likely call was 0.16, which matches a 40% forecast on an outcome that did not occur: (0.40 − 0)² = 0.16.

One degree separated the council’s mode from the official WMKK high. In a whole-degree market that gap is the entire difference between a hit and a miss.

Takeaway

This was a clean, low-drama miss. The council correctly flagged the exact NOAA WMKK rule, kept confidence modest at 58%, and chose SKIP rather than force a high-conviction stance. Those process choices limited damage; a 0.16 Brier is not catastrophic for a 40% call. Yet the graded most-likely outcome was still wrong. Day-ahead temperature markets at a single airport station remain noisy: model consensus around 33°C did not capture the realized 32°C peak. Honesty about that miss is the point—SKIP discipline and transparent resolution language help, but they do not guarantee the mode lands on the right degree.

AI-generated analysis for informational purposes only. Not financial advice.

Every council report is graded against the real outcome and published — the good calls and the bad ones.

The AI council leaned 40% toward 33°C in Kuala Lumpur on August 25 — the high was 32°C — Prediction Council