ChaosWatch
New here? Start here →
Model Arena · depth shallow

Middle East & North Africa · 2026-06-29

One day, one region, several language models — each handed exactly the same headlines and readings, then asked how tense things would be a week later. Because the input is identical, any difference between their answers is a difference between the models.

This page shows what they said. Whether any of it was right is a separate question, answered on the Leaderboard — and the short version there is that none of them beat guessing.

How 'identical evidence' is guaranteed

Every model in a run receives the same rendered prompt over the same evidence payload, and the payload's hash is stored with the run and displayed below. If two models had been shown different material the hashes would differ, so the fairness of the comparison is checkable rather than asserted.

Models that crashed, timed out, or returned unparseable output are persisted as rows and ranked here alongside the successes.

Consensus
45.0
trimmed median over 5 ok score(s); 2 trimmed
Completion
100.0%
5 scored / 5 attempted — failures stay in the denominator
Evidence
9c410c54…d45e
10 headline(s), shared by every model

Ranking

prompt p1depth shallow

Models that failed are listed here too, marked and unscored, rather than quietly dropped. A model that only answers when the question is easy would otherwise look like a model that is good at the question — every leaderboard that hides its failures is really reporting "accuracy among the runs that happened to work".

1
gemini-3.1-pro-previewokUnstable
google
latency 10,004 mstokens in 617tokens out 73
60.0
2
claude-opus-5okUnstable
anthropic
latency 6,289 mstokens in 1,368tokens out 312
55.0
3
deepseek-reasonerokUnstable
deepseek
latency 4,960 mstokens in 874tokens out 304
45.0
4
claude-haiku-4-5okElevated
anthropic
latency 3,288 mstokens in 970tokens out 127
42.0
5
llama-3.3-70b-versatileokElevated
groq
latency 960 mstokens in 823tokens out 95
20.0

Every model in this run returned a parseable verdict, so no failure row is shown. The failure states are rendered by the same component and are covered by tests/model_row_test.tsx.