Kinds of learning
Supervised Learning: Learning From Labeled Examples
Understand how supervised learning connects inputs to target outputs, where labels come from, and why evaluation must match future decisions.
By the end you can
- Define supervised learning in terms of paired inputs and targets
- Identify classification, regression, ranking, and structured prediction as supervised tasks
- Explain how label quality and sampling shape the learned relationship
- Recognize limits of supervised learning when future conditions differ from training data
The basic object is an input–target pair, and somebody made the target
Supervised learning trains a model on examples that pair an input with a target output. That target may be a class, a number, an ordering, a sequence, a mask, or another structured object.
The learner searches for a relationship that performs well on future-like cases. It does not merely memorize the table. Nor does the label guarantee direct access to truth.
The best-documented answer key in medical imaging shows what that reservation is worth. The training target was 128,175 retinal fundus photographs, each graded 3 to 7 times by a panel of 54 US-licensed ophthalmologists and ophthalmology senior residents. Gulshan and colleagues published the result in JAMA in 2016: AUC 0.991 on EyePACS-1 (9,963 images) and 0.990 on Messidor-2 (1,748 images). A later study had a separate clinical validation set graded twice over — once by the majority decision of three ophthalmologists, once by the face-to-face adjudicated consensus of three retinal specialists. The two answer keys disagreed 193 times, 36 of those by at least two grades. Krause and colleagues counted why: “The most common causes were missed MAs (36%), artifacts (20%), and disagreement regarding whether a lesion was an MA or a hemorrhage (16%).”
The scores moved with the key. Measured against the adjudicated consensus, the original Gulshan model scored AUC 0.942 for moderate-or-worse disease. Measured against the retinal specialists' majority decision, the same model scored 0.952. A retrained higher-resolution model, tuned on adjudicated grades, reached 0.986. Not one photograph changed. Only the process that decided what the photographs meant.
Supervision specifies an answer for observed examples; it does not prove the answer-generating process is correct.
Case
Ten benchmarks audited: at least 3.3% label errors in the answer key
That last sentence is measurable. Ten of the most-cited machine-learning benchmarks have had their test sets audited, and the answer keys came back with “an average of at least 3.3% errors across the 10 datasets”. Label errors make up “at least 6% of the ImageNet validation set” alone. Northcutt and colleagues presented the count at NeurIPS in 2021, and crowdsourced review confirmed 51% of the examples their method flagged.
The consequence reaches model selection. On ImageNet with corrected labels, ResNet-18 outperforms ResNet-50 “if the prevalence of originally mislabeled test examples increases by just 6%”. The benchmark had been ranking architectures partly on how well they agreed with mistakes.
Visual
From historical record to future prediction
The supervised workflow converts operational history into examples. It fits a mapping. It then evaluates that mapping on data excluded from fitting.
Five stages carry it. Construct the examples, by choosing the unit, the prediction time, the input features and the target maturity. Fit a model, adjusting parameters to reduce a loss that compares predictions with targets. Validate choices, using separate evidence to select features, capacity, thresholds and training settings. Test the claim on an untouched set that reflects the intended use. Then connect the output to action — decisions, review, abstention, or prioritization.
Each of the failures in this lesson was introduced at one of those five stages, not by the choice of algorithm.
1. Construct examples
Choose the unit, prediction time, input features, and target maturity.
2. Fit a model
Adjust parameters to reduce a loss that compares predictions with targets.
3. Validate choices
Use separate evidence to select features, capacity, thresholds, and training settings.
4. Test the claim
Estimate performance on an untouched set that reflects the intended use.
5. Connect to action
Translate outputs into decisions, review, abstention, or prioritization.
Example
Supervised learning produces more than yes-or-no answers, and the harder targets are bought by the hour
The form of the target determines the immediate prediction task. The more structure the target carries, the more the answer key costs.
Microsoft COCO, published in 2014, contains 2.5 million labeled instances with per-instance segmentations, across 328,000 images in 91 object categories. Cityscapes provides 5,000 images with high-quality pixel-level annotations, plus 20,000 coarsely annotated images from street scenes in 50 cities. Cordts and colleagues state the price per image in the 2016 paper: “Annotation and quality control required more than 1.5 h on average for a single image.”
A pixel-level target is not a different setting on the same machine. It is a different budget. And every one of those hours is a human decision that the next annotator can make differently.
- Binary classification: decide whether a bank transfer requires manual review.
- Multiclass classification: route a support ticket to one of twelve specialist teams.
- Regression: estimate delivery time in minutes rather than selecting a category.
- Ranking: order search results by expected usefulness for a particular query.
- Structured prediction: assign a label to every token, image pixel, or time step — 5,000 Cityscapes images at more than 1.5 h each, 2.5 million segmented instances in COCO.
- Multi-output prediction: estimate several related measurements from one observation.
Comparison
Cost instead of illness: what a convenient proxy cost 200 million people
Convenience decides many targets. Supervised projects often use one that is easier to record than the outcome stakeholders truly value, and the substitution is rarely announced to the people it lands on.
The largest measured case is a commercial risk-prediction algorithm applied, by industry estimates, to roughly 200 million people in the United States each year. Its job was to find the patients who most needed extra care. Its target was not illness. It was health-care cost — recorded for everyone, available immediately, and correlated with need. Obermeyer and colleagues measured the price of that substitution in Science on 25 October 2019. Removing the resulting gap would raise the share of Black patients automatically identified for high-risk care management, at the 97th-percentile threshold, from 17.7% to 46.5%. Their abstract closes on the general point: “We suggest that the choice of convenient, seemingly effective proxies for ground truth can be an important source of algorithmic bias in many contexts.”
The same day, the New York State Department of Financial Services and Department of Health wrote jointly to David S. Wichmann, CEO of UnitedHealth Group, demanding that the company justify or stop using Impact Pro. The gap between a target and an outcome is not an academic distinction. It took days to become a regulator's letter to a named executive.
Three kinds of label sit behind that story. A direct target records the outcome itself, such as a confirmed component failure. It is usually slower or costlier to obtain, comparatively clear to interpret, and still vulnerable to measurement error. A proxy target stands in for a harder outcome, as cost stood in for need. It is often abundant and immediate, it can reward superficial behavior, and it needs product-level validation before anyone trusts it. A policy-created label exists only where a prior decision process looked — fraud confirmed only after an investigation that a rule triggered in the first place. Its coverage depends on historical policy, it can reproduce earlier blind spots, and it needs selective-label analysis. The third kind is the one that looks most like ground truth and is least like it.
Direct target
The recorded label closely matches the intended outcome.
- Example: confirmed component failure
- Usually slower or costlier to obtain
- Interpretation is comparatively clear
- Still vulnerable to measurement error
Proxy target
The label stands in for a harder outcome.
- Example: click as a proxy for usefulness
- Often abundant and immediate
- May reward superficial behavior
- Requires product-level validation
Policy-created label
A prior decision process determines what becomes visible.
- Example: fraud confirmed only after investigation
- Coverage depends on historical policy
- Can reproduce earlier blind spots
- Needs selective-label analysis
Key idea
“Labeled” does not mean “representative”, and in the EU that is now statute
A perfectly labeled historical sample can still mislead. The problem is coverage: it may exclude new regions, devices, customer groups, or rare operating conditions, while supervised learning usually assumes some connection between training examples and future use.
That connection must be argued, tested by slices, and monitored after deployment. Better annotations cannot repair a dataset drawn from the wrong population.
The gap has been measured on chest x-rays. Zech and colleagues trained pneumonia-screening convolutional networks on 158,323 radiographs, and published the study in PLOS Medicine in 2018. The images came from the National Institutes of Health Clinical Center, Mount Sinai Hospital and Indiana University. Each model was then tested outside the system it had been trained on. Performance was significantly lower externally in 3 of 5 natural comparisons. A Mount Sinai model scored 0.802 AUC at home and 0.717 at NIH. A model trained jointly on both fell from 0.931 to 0.815 at Indiana. The same networks identified the source hospital from the image itself. They classified 99.95% of NIH and 99.98% of Mount Sinai radiographs correctly, reading equipment markers and framing outside the lungs. The labels were not the problem. The population was.
Since 12 July 2024 the argument is not only editorial. The EU's Artificial Intelligence Act, Regulation (EU) 2024/1689, was published in the Official Journal of the European Union that day. Article 10(3) states: “Training, validation and testing data sets shall be relevant, sufficiently representative, and to the best extent possible, free of errors and complete in view of the intended purpose.” Article 10(2)(d) requires providers of high-risk AI systems to document “the formulation of assumptions, in particular with respect to the information that the data are supposed to measure and represent”. Article 10(4) requires the data to reflect the specific geographical, contextual, behavioural or functional setting of intended use. A team that cannot name the three hospitals its radiographs came from has not merely skipped a good practice. It cannot answer Article 10(4).
Accurate labels on the wrong cases produce precise evidence for the wrong world.
Position
A benchmark score measures agreement with a test set, not with the world
Accuracy figures are quoted to a tenth of a percent and read as facts about the world. They are facts about one test set, and the test sets everyone quotes have a measured error rate of their own. The audit of ten of the most-cited benchmarks put it at “an average of at least 3.3% errors across the 10 datasets”, and “at least 6% of the ImageNet validation set”, with human review confirming 51% of the candidates the method flagged. That is not a rounding correction. It is larger than most of the margins that get called progress.
The ranking moves with it. On corrected ImageNet labels ResNet-18 comes out above ResNet-50 “if the prevalence of originally mislabeled test examples increases by just 6%”. One of the standard architecture comparisons of the last decade turns on errors in the answer key. Zech's radiographs supply the second question, because those models scored well while reading the hospital rather than the lung, identifying the source system correctly 99.95% and 99.98% of the time.
The same distance opens between a vendor's number and a measured one, on a model that is running in hospitals now. Epic Systems reported its proprietary sepsis prediction model at an AUC of 0.76–0.83. Wong and colleagues validated it externally at Michigan Medicine, across 38,455 hospitalizations of 27,697 patients between 6 December 2018 and 20 October 2019. It scored an AUC of 0.63 (95% CI 0.62–0.64). Their results in JAMA Internal Medicine, in 2021, count the cost in patients and in alerts: “The ESM also did not identify 1709 patients with sepsis (67%) despite generating alerts for an ESM score of 6 or higher for 6971 of all 38 455 hospitalized patients (18%), thus creating a large burden of alert fatigue.” A second, independent validation in 2024 covered 145,885 encounters at two Harris Health county emergency departments in Houston. It found sensitivity 14.7%, specificity 95.3% and positive predictive value 7.6% for sepsis within 6 hours of the alert. One model, two independent validations, and neither of them reproduced the number in the brochure.
Two things therefore have to be true before a published number means anything to you. Somebody can say how the answers it is graded against were produced. And those answers were collected somewhere near the place you intend to operate.
Before you prefer one model to another by a point of accuracy, ask how many of the answers they are being marked against are wrong.
Steps
Review a supervised task before modeling — a regulator now asks for two of these steps in writing
This step comes first. A short design review can expose problems that no algorithm choice will solve. Fix the prediction moment, by stating exactly what information exists when the output must be produced. Define the target, including how it is observed, disputed, delayed, or revised. Map the population, identifying which entities and conditions enter the dataset and which are missing. Set the action for positive, negative, uncertain, or missing predictions. Reserve evaluation evidence that will not influence model or threshold selection.
Two of those five are no longer only good practice in the United States. In January 2025 the US Food and Drug Administration issued draft guidance on AI-enabled device software functions, under Docket No. FDA-2024-D-4488, with comments closing 7 April 2025. It first says what an answer key is: “For the purposes of this guidance, a reference standard is the best available representative truth that can be used to define the true condition for each patient/case/record.” It then requires sponsors to document how the reference standard was established, the uncertainty inherent in it, how equivocal or missing reference-standard results were handled, and how independence of test data from training data was ensured.
Step two of the review, defining the target, and step five, reserving evaluation evidence, are those same demands — with a docket number attached, for anyone shipping a supervised medical device.
1. Fix the prediction moment
State exactly what information exists when the output must be produced.
2. Define the target
Describe how it is observed, disputed, delayed, or revised.
3. Map the population
Identify which entities and conditions enter the dataset and which are missing.
4. Set the action
Explain what happens for positive, negative, uncertain, or missing predictions.
5. Reserve evaluation evidence
Protect data that will not influence model or threshold selection.
When supervised learning is a strong candidate, and how Google Flu Trends stopped being one
Supervised learning fits when historical or newly collected targets meaningfully represent the desired behavior, and future inputs resemble the evaluated population enough for prediction.
It becomes fragile on the label side. Labels may be unavailable, strategically manipulated, policy-dependent, severely delayed, or disconnected from the true objective. Those conditions motivate the approaches developed later in this path.
Google Flu Trends is the counted example. Its targets were sound — the CDC's influenza-like-illness reports — and its inputs were search queries, the model fitted by matching 50 million search terms to 1,152 data points. It ran systematically high. Lazer and colleagues reported that in Science in 2014, and their figure caption states it flatly: “From 21 August 2011 to 1 September 2013, GFT reported overly high flu prevalence 100 out of 108 weeks.” In February 2013 it predicted more than double the CDC proportion of ILI doctor visits. A separate reassessment of the same system, at three geographic scales, had already appeared in PLOS Computational Biology in 2013. Nothing was wrong with the answer key. The relationship between the inputs and it had moved, and 1,152 data points were never enough to notice.
Key takeaways
- Supervised learning uses paired inputs and targets to learn a predictive mapping, and the mapping is only ever as good as the process that produced the targets.
- Targets can be categories, quantities, rankings, sequences, masks, or multiple outputs — and the structured ones are bought by the hour, at more than 1.5 h per Cityscapes image.
- Labels encode measurement, expert judgment, policy, delay, and disagreement rather than unquestioned truth: 54 graders built the retinopathy answer key, and re-grading it by adjudication produced 193 disagreements.
- Representative sampling matters independently of annotation accuracy, and Article 10(3) of Regulation (EU) 2024/1689 has turned that from advice into a legal obligation for high-risk systems.
- Training fit must be separated from validation, testing, and product-level outcomes — Epic's sepsis model was reported at AUC 0.76–0.83 and independently measured at 0.63 (95% CI 0.62–0.64).
- A convenient proxy is a design decision with a measurable cost: removing the cost-for-need gap would raise the share of Black patients auto-identified for high-risk care from 17.7% to 46.5%.