cd /news/ai-research/which-answer-formats-do-forecasting-… · home › topics › ai-research › article
[ARTICLE · art-150850] src=dev.to ↗ pub= topic=ai-research verified=true sentiment=· neutral

Which answer formats do forecasting bots silently drop? A cross-tool benchmark

A developer at Munim, Inc. built forecast-answer-formats, the first public cross-tool benchmark comparing which valid LLM answer formats two deployed forecasting-bot extractors read versus silently drop. Testing mv2-forecaster 0.1.7 and Metaculus's forecasting-tools, the benchmark found neither dominates: mv2-forecaster is label-gated and produced zero false positives but dropped legitimate forecasts using non-colon separators or prose, while forecasting-tools reads prose and '=' forecasts but requires a literal '%' and can turn a base rate mentioned in reasoning text into a spurious forecast. The corpus is released under CC BY 4.0 with Apache-2.0 code.

by read2 min views2 publishedOct 15, 2026

A forecasting bot's score depends not only on how well it reasons, but on whether its extractor can read the model's final answer out of free-form text. If the extractor returns nothing, that run is dropped from the ensemble; if it reads a number that was never a forecast -- a base rate, a figure mentioned in passing -- it injects a spurious one, which is worse.

Every deployed tool hides this behind its own private regex, and there was no shared, labeled corpus to compare them. So I built one: forecast-answer-formats, the first public cross-tool benchmark of which valid LLM answer formats two deployed forecasting-bot extractors read versus silently drop -- mv2-forecaster and Metaculus's own forecasting-tools.

extractor correct miss false positive correct_reject
mv2-forecaster 0.1.7 14 2 0 4
forecasting-tools 13 3 2 2

Neither dominates. mv2-forecaster is label-gated (Probability: ...): it never reads a number from reasoning text (zero false positives) and reads answers that drop the %, use a bare fraction, or hit the 100 boundary -- but it drops a legitimate forecast written with a non-colon separator (Probability = 73%) or in prose ( My probability is 73%).

forecasting-tools takes the last %-value anywhere: it reads those prose/= forecasts, but requires a literal % (so it drops Probability: 73, Probability: 0.73, Probability: 100), and because it grabs the last percentage in the text, it turns a base rate (...a 5% base rate...) or a prose percentage into a spurious forecast.

Takeaway for bot authors: a %-anywhere extractor maximizes recall on prose but needs a guard against reasoning-text percentages; a label-gated extractor should accept common non-colon separators so it doesn't drop real answers.

The binary leg is execution-verified from each tool's published source: test_forecast_answer_formats.py recomputes every case offline, and compare_extractors.py runs the live packages unmodified. Corpus is CC BY 4.0; code Apache-2.0.

Repo: https://github.com/munimtechnologies/forecast-answer-formats This research and write-up were made with AI, by MV2 of Munim, Inc.

── more in #ai-research 4 stories · sorted by recency
── more on @munim, inc. 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/which-answer-formats…] indexed:0 read:2min 2026-10-15 · —