# Probability and uncertainty

- Link: https://arqiv.si/ai/probability-and-uncertainty/
- Published: 2026-10-10T15:12:29-04:00
- Author: Steven Ryan

[Skip to content](https://arqiv.si/ai/probability-and-uncertainty/#main-content)

[arqiv](https://arqiv.si/)

[For educators](https://arqiv.si/teachers/)

Teach

 * [Start here](https://arqiv.si/teachers/)
 * [Lessons & printable kits](https://arqiv.si/teachers/resources/)
 * [Classroom labs](https://arqiv.si/teachers/labs/)
 * [Free 20-minute lesson](https://arqiv.si/teachers/free-ai-lesson/)

Plan

 * [Curriculum guide](https://arqiv.si/teachers/curriculum/)
 * [AI Learning Center](https://arqiv.si/teachers/ai-literacy/)
 * [Future of work unit](https://arqiv.si/future-of-work/)
 * [What the research says](https://arqiv.si/teachers/what-works/)
 * [AI education worldwide](https://arqiv.si/teachers/around-the-world/)

Understand

 * [Think First method](https://arqiv.si/teachers/think-first/)
 * [Our approach](https://arqiv.si/research/#our-method)
 * [AI vocabulary](https://arqiv.si/teachers/ai-vocabulary/)

By role

 * [Counselors](https://arqiv.si/counselors/)
 * [School leaders & PD](https://arqiv.si/schools/)
 * [Speaking & workshops](https://arqiv.si/speaking/)
 * [Products](https://arqiv.si/products/)

[Learn AI](https://arqiv.si/ai/topics/)

Start

 * [All AI topics](https://arqiv.si/ai/topics/)
 * [The AI journey, from zero](https://arqiv.si/ai/)
 * [Using AI well](https://arqiv.si/ai/talking-to-ai/)
 * [AI builds](https://arqiv.si/ai-builds/)

AI in the world

 * [Space](https://arqiv.si/space/)
 * [Weather](https://arqiv.si/weather/)
 * [Health](https://arqiv.si/health/)
 * [Engineering](https://arqiv.si/engineering/)
 * [Farming](https://arqiv.si/farming/)
 * [Quantum](https://arqiv.si/quantum/)

What it means

 * [Future of work](https://arqiv.si/future-of-work/)
 * [Your AI path](https://arqiv.si/ai/your-path/)
 * [Research, explained](https://arqiv.si/research/)

[Games & labs](https://arqiv.si/games/)[Research](https://arqiv.si/research/)[Blog](https://arqiv.si/blog/)
[About](https://arqiv.si/about/)

[Search or ask](https://arqiv.si/ai/topics/)[Newsletter](https://arqiv.si/newsletter/)
[ARQIV.FM ↗](https://arqiv.fm/)

Menu

For educators

[For educators: start page →](https://arqiv.si/teachers/)

Teach

 * [Start here](https://arqiv.si/teachers/)
 * [Lessons & printable kits](https://arqiv.si/teachers/resources/)
 * [Classroom labs](https://arqiv.si/teachers/labs/)
 * [Free 20-minute lesson](https://arqiv.si/teachers/free-ai-lesson/)

Plan

 * [Curriculum guide](https://arqiv.si/teachers/curriculum/)
 * [AI Learning Center](https://arqiv.si/teachers/ai-literacy/)
 * [Future of work unit](https://arqiv.si/future-of-work/)
 * [What the research says](https://arqiv.si/teachers/what-works/)
 * [AI education worldwide](https://arqiv.si/teachers/around-the-world/)

Understand

 * [Think First method](https://arqiv.si/teachers/think-first/)
 * [Our approach](https://arqiv.si/research/#our-method)
 * [AI vocabulary](https://arqiv.si/teachers/ai-vocabulary/)

By role

 * [Counselors](https://arqiv.si/counselors/)
 * [School leaders & PD](https://arqiv.si/schools/)
 * [Speaking & workshops](https://arqiv.si/speaking/)
 * [Products](https://arqiv.si/products/)

Learn AI

[Learn AI: start page →](https://arqiv.si/ai/topics/)

Start

 * [All AI topics](https://arqiv.si/ai/topics/)
 * [The AI journey, from zero](https://arqiv.si/ai/)
 * [Using AI well](https://arqiv.si/ai/talking-to-ai/)
 * [AI builds](https://arqiv.si/ai-builds/)

AI in the world

 * [Space](https://arqiv.si/space/)
 * [Weather](https://arqiv.si/weather/)
 * [Health](https://arqiv.si/health/)
 * [Engineering](https://arqiv.si/engineering/)
 * [Farming](https://arqiv.si/farming/)
 * [Quantum](https://arqiv.si/quantum/)

What it means

 * [Future of work](https://arqiv.si/future-of-work/)
 * [Your AI path](https://arqiv.si/ai/your-path/)
 * [Research, explained](https://arqiv.si/research/)

 * [Games & labs](https://arqiv.si/games/)
 * [Research](https://arqiv.si/research/)
 * [Blog](https://arqiv.si/blog/)
 * [About](https://arqiv.si/about/)

[Get the newsletter](https://arqiv.si/newsletter/)

 1. [ARQIV / HOW MACHINES LEARN](https://arqiv.si/ai/topics/)
 2. [**01**Reinforcement learning](https://arqiv.si/ai/reinforcement-learning/)
 3. [**02**Search & planning](https://arqiv.si/ai/search-and-planning/)
 4. [**03**Neural-network families](https://arqiv.si/ai/neural-network-families/)
 5. [**04**Probability](https://arqiv.si/ai/probability-and-uncertainty/)
 6. [**05**Embeddings](https://arqiv.si/ai/embeddings/)

Go deeper · How machines learn

# How sure should an AI _be?_

As sure as the evidence allows, and no surer. A probability is a number from 0 to
1 that says how often something happens in situations like this one. A trustworthy
system gives probabilities that match what really happens, and a careful user asks
what the number is “out of”: how common the thing was to begin with.

Grades 9+20 minutesFractions and percentagesGrades 6–8: count, don’t divide

What you will be able to do

Turn percentages into counts out of 1,000 to find the chance that a flagged item
is really positive, explain why base rates matter, check whether forecasts are calibrated,
and tell correlation from causation.

Before you start

Read [How to evaluate AI](https://arqiv.si/ai/evaluating-ai/) first (false positives,
precision and recall). You need to be comfortable with fractions and percentages.

1 · You have already seen this

## The forecast said _70% chance of rain_

Weather apps put a number on tomorrow, and many of us check it before deciding on
an umbrella.

A forecast of “70% chance of rain” sounds simple, but people read it in different
ways. Some think it means rain for 70% of the day, or over 70% of the town. A U.
S. National Weather Service forecast means that, on days like this one, the place
gets at least a little rain about 7 times out of 10.

AI systems give numbers like this all the time. A spam filter gives each email a
score, and a language model gives every possible next word a chance. Each of these
is a **probability**, and reading one well means asking how sure the system should
be and how common the thing was to begin with. The rest of this page shows how that
works, lets you try it, and shows where it goes wrong.

2 · What happens, step by step

## From a score to _a careful reading_

Reading a probability from an AI system in five steps. The three sections after 
this one go deeper into step 1, steps 2 and 3, and step 4. After the lab, one more
goes deeper into step 5.

How to read a probability

### Five steps

 1. 1 · Ask which way roundThese two questions sound alike and can have very different
    answers: “Of all the spam, how much gets flagged?” and “Of everything flagged, 
    how much is spam?”
 2. 2 · Start from the base rateAsk how common the thing is before any test. Imagine
    1,000 cases and split them into the two groups.
 3. 3 · Count the flagsApply the catch rate to one group and the false-alarm rate to
    the other, then add the flags. Counting like this is much easier than multiplying
    percentages.
 4. 4 · Check the number is honestA probability is only useful if it is **calibrated**:
    across many cases where a system said 70%, it should be right about 70% of the 
    time. One case cannot show that.
 5. 5 · Don’t read in a causeA model learns what goes together in its data. It cannot
    tell, on its own, which one causes which.

Going deeper · step 1

## A number for _how often_

Probability is the language AI systems use for uncertainty, and the place where 
people most often misread them.

A **probability** runs from 0 (never) to 1 (always), often written as a percentage.
When a U.S. National Weather Service forecast says “70% chance of rain,” it means
that, on days like this, the place will get at least a little measurable rain about
7 times out of 10. It does not mean rain for 70% of the day or over 70% of the town.

AI systems output probabilities all the time. A spam filter gives each email a score
such as 0.92. A language model gives every possible next word a probability, and
all of them add up to 1: that list is a **probability distribution**, and the model
picks from it (see [How transformers work](https://arqiv.si/ai/transformers/#step5)).

Most useful probabilities are **conditional**: the chance of one thing _given that_
another is true. People write P(spam | flagged), read “the probability of spam, 
given that the email was flagged.” Swap the two sides and you get a different question,
P(flagged | spam): how often spam gets flagged. Mixing these up is one of the most
common mistakes in reading any test, human or AI.

Two questions that sound alike

### Which way round?

**P(flagged | spam)**: of all the spam, how much gets flagged? This is the filter’s
_catch rate_ (recall).

**P(spam | flagged)**: of everything flagged, how much is really spam? This is what
you want to know when you look at your spam folder (precision).

They can be very different, as the worked example shows.

Going deeper · steps 2 and 3

## How common was it _to begin with?_

The base rate is how common something is before any test. It changes what a positive
result means.

Predict first

A filter catches 90% of spam and wrongly flags only 5% of real emails. In a week
when just 2% of emails are spam, an email gets flagged. Is it more likely to be 
spam or real?

Show the answer

**More likely real.** Only about 27% of flagged emails are spam that week. With 
so little spam around, the small false-alarm rate applied to the huge number of 
real emails produces more flags than the spam does. The worked example counts it
out.

Worked example

### Out of 1,000 emails: is a flagged email really spam?

 1. The filterA made-up spam filter catches **90%** of spam and wrongly flags **5%**
    of real emails. Both sound good.
 2. Busy week: 20% spamOf 1,000 emails, 200 are spam and 800 are real. Caught: 90% 
    of 200 = 180. False alarms: 5% of 800 = 40. Flagged in total: 180 + 40 = 220.
 3. Chance a flagged one is spam180 ÷ 220 ≈ 82%. Not 90%: some flags land on real emails.
 4. Quiet week: 2% spamSame filter. 20 spam, 980 real. Caught: 90% of 20 = 18. False
    alarms: 5% of 980 = 49. Flagged: 18 + 49 = 67.
 5. Chance a flagged one is spam18 ÷ 67 ≈ 27%. Most flagged emails are now real. The
    filter did not get worse; spam got rarer, so the 5% of false alarms outnumber the
    real catches.
 6. The lessonP(flagged | spam) = 90% in both weeks. P(spam | flagged) was 82%, then
    27%. The two “given that” numbers are different questions, and the base rate links
    them.

The filter and the emails are made up. Counting out of 1,000 (“natural frequencies”)
makes this much easier than multiplying percentages.

Ignoring the base rate is called **base-rate neglect**, and it is easy to fall into
because the filter’s “90%” is the number people remember. The fix is to count: imagine
1,000 cases, split them by the base rate, then apply the catch rate and the false-
alarm rate to each group. Researchers have found that people reason far better with
counts like these than with percentages.

The same logic applies to any detector of rare things: fraud alerts, factory defect
checks, AI-text detectors. A detector that is “95% accurate” can still be wrong 
about most of the cases it flags if what it looks for is rare. The ARQIV [health threshold lab](https://arqiv.si/health/#lab)
shows the same trade-off with a synthetic screening example.

Going deeper · step 4

## When it says 70%, _is it right 70% of the time?_

A probability is only useful if it is honest. Checking that is called calibration.

A forecaster is **calibrated** if, across all the days it said 70%, it rained on
about 70% of them, and the same for 10%, 40% or any other number. You cannot judge
calibration from one day: a 70% forecast followed by a dry day is not wrong, because
dry days are expected 3 times in 10. You need many forecasts, grouped by what they
said.

Modern neural networks are often _overconfident_: researchers have found that their
top-choice probabilities tend to be higher than their real accuracy, unless they
are adjusted after training. And a chatbot’s confident tone is not a probability
at all; fluent text sounds just as sure when it is wrong. [How to evaluate AI](https://arqiv.si/ai/evaluating-ai/)
shows calibration as part of testing a model.

**Now check _your own_ calibration.** People are often overconfident too. [How Sure Are You?](https://arqiv.si/future-of-work/how-sure/)
asks ten true-or-false questions, records how sure you are, and draws your own calibration
chart.

3 · Try it

## Count the flags, _then check the forecasts_

Part 1 is about base rates; part 2 is about calibration. Both use only counting.

Lab

### How many flagged emails are really spam?

Each square is one of 1,000 made-up emails. Move the sliders and watch how many 
flagged emails are really spam. Then compare two made-up weather apps.

 Simulated in your browser with made-up emails and forecasts. Nothing is stored.

#### Part 1 · The frequency grid

Spam rate (base rate): **20**% of emails

Catch rate: flags **90**% of spam

False-alarm rate: flags **5**% of real emails

 * spam, flagged
 * real, flagged (false alarm)
 * spam, missed
 * real, not flagged

#### Part 2 · Calibration check

Two made-up weather apps, each tested on its own made-up set of 200 days. Each dot
shows, for one forecast number, how often it really rained. On the dashed line, 
the forecasts are honest.

Three challenges

 1. Keep the filter at 90% and 5%. Find the spam rate where a flagged email is about
    a 50–50 coin flip.
 2. At 2% spam, which helps more: raising the catch rate to 100%, or lowering the false-
    alarm rate to 1%?
 3. On which forecast does App B differ most from what happened? Would you trust its“
    90%”?

**Part 1.** A made-up spam filter catches 90% of spam and wrongly flags 5% of real
emails. Here is what happens to 1,000 emails as spam becomes more or less common.

Same filter, five base rates (1,000 made-up emails)| Spam rate | Spam emails | Spam caught | Real emails flagged | All flagged | Flagged that are spam | 
| 2% | 20 | 18 | 49 | 67 | 18 ÷ 67 = 27% | 
| 5% | 50 | 45 | 48 | 93 | 45 ÷ 93 = 48% | 
| 10% | 100 | 90 | 45 | 135 | 90 ÷ 135 = 67% | 
| 20% | 200 | 180 | 40 | 220 | 180 ÷ 220 = 82% | 
| 50% | 500 | 450 | 25 | 475 | 450 ÷ 475 = 95% |

**Part 2.** Two made-up weather apps, each tested on its own made-up set of 200 
days. A calibrated app’s “30%” days should be rainy about 30% of the time.

Forecast vs what happened| Forecast | Days | App A: rainy days | App B: rainy days | 
| 10% | 30 | 3 (10%) | 9 (30%) | 
| 20% | 25 | 6 (24%) | 9 (36%) | 
| 30% | 20 | 6 (30%) | 8 (40%) | 
| 40% | 20 | 8 (40%) | 9 (45%) | 
| 50% | 15 | 7 (47%) | 8 (53%) | 
| 60% | 20 | 12 (60%) | 10 (50%) | 
| 70% | 25 | 17 (68%) | 14 (56%) | 
| 80% | 25 | 20 (80%) | 15 (60%) | 
| 90% | 20 | 18 (90%) | 13 (65%) |

Correlation vs causation

## Moving together _is not causing_

Machine learning finds patterns that go together. It cannot tell, on its own, which
one causes which.

In the made-up beach town, weeks with more ice cream sold also had more sunburns.
The two are strongly **correlated**. Does ice cream cause sunburn? No: both go up
with a third thing, sunny hours. A hidden cause like this is called a **confounder**.

A model trained on this data could predict sunburns from ice cream sales quite well,
and that is fine as long as nothing changes. But if the shop runs a half-price sale
on a cloudy week, sales jump and the model predicts a wave of sunburns that never
comes. Models learn what goes together in their data, not why. To find a cause you
need more: an experiment where you change one thing on purpose, or careful reasoning
about what else could explain the pattern.

The same trap appears in [data and datasets](https://arqiv.si/ai/data-and-datasets/):
a model that learned a background or a watermark instead of the object itself. [Train the Machine](https://arqiv.si/teachers/labs/#train)
lets students find one.

Six made-up summer weeks in a beach town| Week | Sunny hours | Ice creams sold | Sunburns reported | 
| Week 1 | 35 | 380 | 9 | 
| Week 2 | 12 | 150 | 3 | 
| Week 3 | 50 | 520 | 14 | 
| Week 4 | 28 | 290 | 8 | 
| Week 5 | 20 | 230 | 4 | 
| Week 6 | 41 | 410 | 12 |

Optional: the correlation coefficient r between ice creams and sunburns in this 
table is about 0.97 (1 would be a perfect straight-line match). A high r still says
nothing about cause.

4 · Common mix-ups

## Numbers that are _easy to misread_

Four ideas that trip people up, and what to think instead.

 * **Mix-up:** The filter catches 90% of spam, so a flagged email is 90% likely 
   to be spam.
 * **Better:** That swaps P(flagged | spam) for P(spam | flagged). The second depends
   on the base rate; it was 82% in a busy week and 27% in a quiet one.
 * **Mix-up:** The forecast said 70% rain and it stayed dry, so the forecast was
   wrong.
 * **Better:** One day cannot show that. A calibrated 70% forecast should be dry
   on about 3 days in 10.
 * **Mix-up:** If two things rise together, one causes the other.
 * **Better:** They may share a hidden cause, like sunshine for ice cream and sunburn,
   or the cause may run the other way.
 * **Mix-up:** An AI that says 99% is almost certainly right.
 * **Better:** Only if it is calibrated. Many models are overconfident, and a chatbot’s
   confident wording is not a measured probability.

5 · Check yourself

## Three _quick questions_

Answer in your head or on paper before you open each one.

 1.  A made-up smoke alarm sounds for 95% of real fires and also for 10% of burnt-toast
     moments. In a school kitchen, 20 of 1,000 smoky moments are real fires. When the
     alarm sounds, what is the chance it is a real fire?
 2.  Check your answer
 3.  Fires: 95% of 20 = 19 alarms. Toast: 10% of 980 = 98 alarms. Total 19 + 98 = 117
     alarms, so 19 ÷ 117 ≈ **16%**. Most alarms are toast, because fires are rare. 
     That does not make the alarm useless: missing a fire is far worse than a false
     alarm, so a high catch rate is the right choice here.
 4.  A made-up weather app said “30% chance of rain” on 40 days, and it rained on 22
     of them. Is it calibrated at 30%?
 5.  Check your answer
 6.  No. 22 ÷ 40 = **55%**, far above 30%. On those days the app was too sure it would
     stay dry (underconfident about rain). With 40 days there is some luck involved,
     but a gap that large is a real warning sign.
 7.  A made-up survey finds that students who use a homework app more often have higher
     grades. Does the app cause the higher grades?
 8.  Check your answer
 9.  Not necessarily. Students who already work hard may use the app more (a confounder:
     motivation), or good grades might make students enjoy using it (cause the other
     way round). A fairer test assigns the app to some students at random and compares
     results.

For grades 6–8

## Count, _don’t divide_

The whole idea works with 100 squares on paper and no percentages.

20 minutes · pairs

### The 100-email grid

 1. Draw a 10 × 10 grid: each square is an email. Color 10 squares red: they are spam.
 2. The filter catches 9 of the 10 spam emails: circle 9 red squares.
 3. It also flags 1 in every 10 real emails by mistake: circle 9 of the 90 white squares.
 4. Count the circles: 18. How many are really spam? 9. So a flagged email is spam 
    half the time.

Talk about it

### Why only half?

Good answers notice that there were many more real emails than spam, so even a few
mistakes on them add up to as many circles as the real catches. Then try it with
30 red squares and see the answer change.

Honest limits

## What this page _leaves out_

What this page leaves out

This page counts instead of using formulas. Bayes’ rule, which does the same calculation
with probabilities, gets no space; nor do probability distributions for numbers (
like the bell curve), uncertainty ranges on predictions, or scores for forecasts
such as the Brier score (the [How Sure Are You?](https://arqiv.si/future-of-work/how-sure/)
lab explains and computes one for your own answers). Real calibration checks need
many more cases than 200 days. Proving a cause usually needs experiments or careful
causal methods, a field of its own.

Where to go next

## Uncertainty _everywhere_

Next in this branch

### How can meaning become a place on a map?

Embeddings, similarity and why close is not the same as correct.

Foundations · 06

### Good at what, for whom, compared with what?

Precision, recall, thresholds and calibration in testing.

Thresholds at work

### Where should the AI draw the line?

Misses vs false alarms in a synthetic screening lab.

Sources

## Where this comes from

 1. [National Weather Service, Atlanta/Peachtree City office, “What is the meaning of PoP?”: what a probability-of-precipitation forecast says.](https://www.weather.gov/ffc/pop)
 2. [Gerd Gigerenzer and Ulrich Hoffrage (1995), “How to improve Bayesian reasoning without instruction: Frequency formats,” _Psychological Review_: counting cases makes conditional probability easier.](https://doi.org/10.1037/0033-295X.102.4.684)
 3. [Daniel Kunin et al., Brown University, _Seeing Theory_: interactive chapters on probability, compound events and conditional probability.](https://seeing-theory.brown.edu/)
 4. [scikit-learn User Guide, “Probability calibration”: calibration curves that compare predicted probabilities with observed frequencies.](https://scikit-learn.org/stable/modules/calibration.html)
 5. [Chuan Guo et al. (2017), “On calibration of modern neural networks”: modern networks are often overconfident, and simple adjustments help.](https://arxiv.org/abs/1706.04599)
 6. [Stuart Russell and Peter Norvig, _Artificial Intelligence: A Modern Approach_, 4th edition, table of contents: the chapters on quantifying uncertainty and probabilistic reasoning.](https://aima.cs.berkeley.edu/contents.html)

AI words on this page

[Probability distribution](https://arqiv.si/teachers/ai-vocabulary/#probability-distribution),
[Conditional probability](https://arqiv.si/teachers/ai-vocabulary/#conditional-probability),
[Base rate](https://arqiv.si/teachers/ai-vocabulary/#base-rate), [Calibration](https://arqiv.si/teachers/ai-vocabulary/#calibration),
[Correlation vs causation](https://arqiv.si/teachers/ai-vocabulary/#correlation-vs-causation),
[False positive](https://arqiv.si/teachers/ai-vocabulary/#false-positive), [Precision and recall](https://arqiv.si/teachers/ai-vocabulary/#precision-and-recall),
[Confusion matrix](https://arqiv.si/teachers/ai-vocabulary/#confusion-matrix), [Next-word prediction](https://arqiv.si/teachers/ai-vocabulary/#next-word-prediction),
[Evaluation](https://arqiv.si/teachers/ai-vocabulary/#evaluation)

All definitions live in one place: [AI words in plain language →](https://arqiv.si/teachers/ai-vocabulary/)

Review status

Written by ARQIV. Last checked October 2026. Independent subject review and classroom
pilots are still to come, so treat the activities as drafts and [tell us](https://arqiv.si/ai/probability-and-uncertainty/info@arqiv.fm?subject=AI%20foundations%20correction)
about anything that is wrong or unclear.

[← Previous**Neural-network families**](https://arqiv.si/ai/neural-network-families/)
[Next →**Embeddings**](https://arqiv.si/ai/embeddings/)

[arqiv](https://arqiv.si/)

A little understanding changes everything.

[LISTEN: ARQIV.FM, OUR WEEKLY SHOW ↗](https://arqiv.fm/)

Educators

 * [Start here](https://arqiv.si/teachers/)
 * [Lessons & kits](https://arqiv.si/teachers/resources/)
 * [Curriculum](https://arqiv.si/teachers/curriculum/)
 * [Labs](https://arqiv.si/teachers/labs/)
 * [AI vocabulary](https://arqiv.si/teachers/ai-vocabulary/)

For your role

 * [Counselors](https://arqiv.si/counselors/)
 * [School leaders & PD](https://arqiv.si/schools/)
 * [Speaking & workshops](https://arqiv.si/speaking/)
 * [Products](https://arqiv.si/products/)

Learn

 * [Learn AI](https://arqiv.si/ai/topics/)
 * [Games & labs](https://arqiv.si/games/)
 * [Future of work](https://arqiv.si/future-of-work/)
 * [Research](https://arqiv.si/research/)
 * [Headlines](https://arqiv.si/news/)

ARQIV

 * [About & corrections](https://arqiv.si/about/)
 * [Our approach](https://arqiv.si/research/#our-method)
 * [Newsletter](https://arqiv.si/newsletter/)
 * [Privacy](https://arqiv.si/privacy-policy/)
 * [Get in touch](https://arqiv.si/ai/probability-and-uncertainty/info@arqiv.fm)

Classroom activities collect no student data.[info@arqiv.fm](https://arqiv.si/ai/probability-and-uncertainty/info@arqiv.fm)
