Takeaways from the Metaculus AI Progress Tournament

This post was originally shared on the Effective Altruism Forum. You can see further discussion on the original post.

In 2019, Open Philanthropy commissioned a set of forecasts on AI progress from Metaculus.^[1]The questions were run in parallel on Hypermind, but this analysis will focus exclusively on the Metaculus forecasts. The forecasting questions had time horizons between 6 months and >6 years. As of June 2023,^[2]I started writing this analysis in April 2023. I last updated it in June 2023. 69 of the 111 questions had been resolved unambiguously. In this post, I analyze the accuracy of these forecasts as a function of question (sub)category, crowd size, and forecasting horizon. Unless otherwise indicated, my analyses are about Metaculus’ proprietary aggregate forecast (“the Metaculus prediction”) evaluated at the time the question closed.

1. Related work

1. This analysis published 2 years ago (July 2021) looked at 64 resolved AI questions and concluded there was weak but ultimately inconclusive evidence of bias towards faster progress.
2. A more recent analysis from March 2023 found that Metaculus had a worse Brier score on (some) AI questions than its average across all questions and presented a few behavioral correlates of accuracy within AI questions, e.g. accuracy was poorer on questions with more updates and when those updates were less informative in a certain technical sense (see post for details).
3. Metaculus responded to the previous post with a more comprehensive analysis that included all resolved AI questions (152 in total, 64 of which were binary and 88 continuous). They show that performance was significantly better than chance for both question types and marginally better than was claimed in the previous analysis (which relied on a smaller sample of questions), though still worse than the average for all questions on the site.

The analysis I present below has some overlaps with those three. But it fills an important gap by studying whether there is systematic over- or under-optimism in Metaculus’s AI progress predictions, using data from a recent tournament that had monetary incentives and thus (presumably) should have resulted in more careful forecasts.

2. Key takeaways

These results haven’t been thoroughly vetted by anyone else. The conclusions I draw represent my views, not Open Phil’s.

1. Progress on benchmarks was underestimated, while progress on other proxies (compute, bibliometric indicators, and, to a lesser extent, economic indicators) was overestimated. [More]
   1. This is consistent with a picture where AI progresses surprisingly rapidly on well-defined benchmarks, but the attention it receives and its “real world” impact fail to keep up with performance on said benchmarks.
   2. However, I see a few problems with this picture:
      1. It’s unclear to me how some of the non-benchmark proxies are relevant to AI progress, e.g.
         1. The TOP500 compute benchmark is mostly about supercomputers that (AFAICT) are mostly used to run numerical simulations, not to accelerate AI training and inference. In fact, some of the top performers don’t even have GPUs.
         2. The number of new preprints in certain ML subfields over short (~6-month) time horizons may be more dependent on conference publication cycles than underlying growth.
      2. Most of these forecasts came due before or very soon after the release of ChatGPT and GPT-4 / Bing, a time that felt qualitatively different from where we are today.
2. Metaculus narrowly beats chance and performs worse in this tournament than on average across all continuous questions on the site, despite the prize money. This could indicate that these questions are inherently harder, or that they drove less or lower-quality engagement. [More]
3. There’s no strong evidence that performance was significantly worse on questions with longer horizons (<1 year vs ~2 years). [More]
4. I see no clear pattern behind the biggest misses, but I provide plausible postmortems for some of them. [More]

3. Results

All calculations are in this spreadsheet and this notebook. If you find that something is wrong or missing, please let me know.

3.1 Bias

Does Metaculus over- or underestimate AI progress?

1. Pooling all tournament questions together, there is no evidence of bias: the CDF^[3]I reverse-coded the questions where lower numbers meant faster progress (e.g. the benchmarks measuring perplexity) so that a higher/lower CDF could be interpreted consistently as pessimism/optimism. of the Metaculus prediction at close time evaluated at the true value is uniformly distributed,^[4]A Kolmogorov-Smirnov test couldn’t reject the null hypothesis “the data were sampled from a uniform distribution on (0,1)” at $\alpha =\mathrm{0.05.}$ as expected for an unbiased predictor.
2. However, this picture changes if we break down the data by question category:^[5]There were essentially four question categories in this tournament:* Economic indicators, e.g. market cap of certain tech companies, weight of IT in the S&P 500.* Bibliometric indicators, all of them of the form “How many papers of <ML subfield> will be published on the arXiv before … Continue reading
   1. Progress on benchmarks was underestimated.
   2. Progress on compute and number of relevant publications was overestimated.
   3. Predictions about economic indicators were also slightly overestimated, although consistent with no bias at any conventional significance threshold.
   4. The difference in “optimism” between benchmarks and the other three categories was significant (perhaps with the exception of economics; see footnote).^[6]I tested this in two ways: (i) the t-distributed 95% confidence interval for CDF(true value) of the benchmark category doesn’t overlap with bibliometrics or compute, and the overlap with economics is rather small (2 percentage points); and (ii) a categorical OLS regression with the benchmarks … Continue reading

3.2 Accuracy

1. Did Metaculus outperform chance?
   1. The average log score at question close was 0.701 (Median: 0.868, IQR: [-0.165, 1.502]^[7]This is the observed interquartile range of the data, not a confidence interval on the mean or median.) compared to an average of 2.17 for all resolved continuous questions on Metaculus.^[8]As indicated in their track record page as of Jun 5, 2023.
   2. About 70% of the predictions at question close had a positive log score, i.e. they were better than predicting a maximally uncertain uniform distribution over the relevant range (chance level).
2. Does accuracy change as a function of time until resolution?
   1. The log score of the Metaculus prediction at question close didn’t change as a function of the prediction horizon, i.e. the time elapsed between question close and resolution. The result doesn’t change after controlling for question category.^[9]I fit the models `log_score ~ horizon` and `log_score ~ horizon + C(category)` using Python’s statsmodels OLS method. The 95% interval for the coefficient of `horizon` is [-0.002, 0.002] in both.
3. Does accuracy improve with more forecasts or unique forecasters?
   1. Log score at close time was not correlated with the number of predictions or the number of unique forecasters on the relevant question.
   2. This is in mild tension with this other result that looked at a larger subset of Metaculus questions, and with the broader literature on the wisdom of the crowd. However,
      1. As noted by the author, the Metaculus analysis is probably confounded by time affecting both the number of people who’ve forecasted on the question and the information available to make those forecasts.
      2. The range of unique forecasters in our dataset (25-100) is probably past the point of vanishingly low diminishing returns.^[10]See how the curves in figures 1 and 3 here tap out at <30 – although the metric of success is not a log score, so I’m not sure how much this applies to our case. Another line of evidence comes from this claim by Manifold Markets; they say their calibration page only includes markets with … Continue reading

3.3 Some narrative speculations

1. What were the biggest surprises? Were they near misses?
   1. The biggest surprises were questions about compute, economic indicators, and SOTA performance on text and image benchmarks. I don’t see an obvious common cause behind them. I added narrative speculations in the notes column of the spreadsheet for the top 10 misses.
   2. I don’t think these were near misses. None of them felt like “a paper came out just the day before resolution and it blew the SOTA out of the water”.
   3. Overoptimistic forecasts were very much so. When a forecast was too bullish, it was more likely that the true value ended up below the 10th percentile of the CDF than between the 10th and 50th percentiles.

4. Appendix: Comparison with previous tournament

In late 2019 and early 2020, Metaculus ran a series of questions about AI progress on a separate subdomain. These questions were not published to the top domain. Of the 34 questions that have been resolved, 23 were binary and 11 were continuous.

The people making predictions on these questions were a mix of top Metaculus forecasters and AI safety experts. How well did they do?

1. Their average log score on continuous questions was 1.766 vs 0.701 in the AI progress tournament. Their average log score on binary questions was 0.246.
2. There was no evidence of bias in their predictions – this is true of both continuous and binary questions. The number of questions is too small to draw any meaningful conclusions about bias broken down by category.
3. There was very weak evidence of underconfidence on binary questions.^[11]I fitted the logistic regression `outcome ~ Bernoulli(inverse_logit(log odds))`. The inverse of the slope in this model can be interpreted as a measure of overconfidence – if it’s >1, it means the forecasts are extremized with respect to the true probability. I found this number was 0.483 … Continue reading

Thanks to Joshua Blake, David Manheim, Luke Muehlhauser, and Jaime Sevilla for helpful feedback, and to Britney Budiman for editing and formatting support. All errors are mine.

Special thanks to Peter Mühlbacher for catching some errors post-publication.