Skip to content
AI.info

Computer vision

Vision Dataset Design, Annotation, and Provenance

Design vision datasets around units, capture conditions, annotation policy, provenance, rights, and independent evaluation.

By the end you can

Key idea

A million images can still describe one narrow world

A dataset may contain enormous volume while repeating the same devices, locations, backgrounds, and people. Random image-level splitting can then place near-duplicates from one event into both training and test. Effective sample size depends on independent variation relevant to deployment, not the count of files.

Twelve of the field's standard collections turned out to carry a fingerprint. Torralba and Efros measured it in 2011, and the protocol was deliberately blunt: “We randomly sampled 1000 images from the training portions of each of the 12 datasets, and trained a 12-way linear SVM classifier.” They tested on 300 random test images per dataset and repeated the whole procedure 20 times. The classifier's only job was to name which of the twelve collections an image had come from. That should be impossible if the twelve are all just samples of the visual world. Chance was 1/12. The best of four descriptors reached 39%: “the best classifier performs rather well at 39% (chance is 1/12 = 8%)”. Each dataset, they concluded, “possesses a unique, identifiable” signature. A model trained inside one collection can learn that signature instead of the task.

The comfortable reading is that this was an artefact of small hand-curated collections from 2011, cured by scraping the web at scale. It was not. In 2024 Liu and He re-ran the same experiment on three modern web-scale datasets — YFCC, CC and DataComp. With three sources, chance is 33.3%. The classifier reached 84.7%. Fifteen years and several orders of magnitude of data later, the fingerprint is easier to read, not harder.

Twelve curated datasets were identifiable at 39% against 8% chance; three web-scale ones at 84.7% against 33.3%.

Figure

A collection carries a signature its pictures were never meant to have — and a test set rebuilt by the same process still costs accuracy.

Visual

The evidence stack behind a visual label

An annotation is the final layer of several prior design choices, and a defect in a lower layer survives every improvement made above it. No annotation policy, however careful, can describe a population the sampling process never reached.

Two standard face benchmarks turned out to be lopsided at that bottom layer. Buolamwini and Gebru measured the composition and reported it in 2018: “We find that these datasets are overwhelmingly composed of lighter-skinned subjects (79.6% for IJB-A and 86.2% for Adience) and introduce a new facial analysis dataset which is balanced by gender and skin type.” On their balanced set, commercial gender classifiers erred on up to 34.7% of darker-skinned females against 0.8% for lighter-skinned males. The skew sits in the deployment-population layer and is visible there only as percentages of a benchmark's composition. It came out the other end as a forty-fold gap in error rate.

A national metrology institute reached the same place by a different route. NIST tested 189 algorithms from 99 developers on 18.27 million images of 8.49 million people. Its December 2019 report found false positive rates varying across demographic groups by factors of 10 to beyond 100. Two independent measurement efforts, one academic and one governmental, put numbers on the same layer of the stack.

FigureLayers · 5 layers
  1. 01

    Deployment population

    The people, places, devices, objects, and conditions the system will encounter.

  2. 02

    Sampling process

    Rules determine which events become captured assets and which remain invisible.

  3. 03

    Media asset

    Frames, clips, volumes, tiles, and crops preserve different context and dependencies.

  4. 04

    Annotation protocol

    Ontology, instructions, tools, visibility rules, and adjudication shape the target.

  5. 05

    Dataset release

    Splits, versions, licenses, provenance, and documentation define usable evidence.

Comparison

Choose the annotation that answers the actual question

Different label forms impose different cost, ambiguity, and model requirements. The choice is a contract. It fixes what the model can be asked to output, what the annotator has to decide, and which disagreements the guideline will have to resolve later.

FigureComparison · 5 columns

Image-level label

Describes an entire image or crop.

  • Lowest spatial precision
  • Fastest annotation
  • Risk: background shortcuts
  • Use case: scene or product class

Bounding box

Approximates object extent with a rectangle.

  • Supports localization
  • Moderate annotation cost
  • Risk: ambiguous visible extent
  • Use case: detection and counting

Pixel mask

Marks a semantic region or individual instance.

  • High spatial precision
  • Expensive quality control
  • Risk: boundary inconsistency
  • Use case: measurement and dense prediction

Keypoints or landmarks

Marks named locations with visibility states.

  • Captures structured geometry
  • Requires point definitions
  • Risk: occlusion disagreement
  • Use case: pose and alignment

Pairwise or track identity

Links assets that refer to the same entity.

  • Supports retrieval and tracking
  • Needs identity policy
  • Risk: accidental identity leakage
  • Use case: re-identification

Example

Questions an annotation guide must answer explicitly

Ambiguous instructions create systematic label noise that no optimizer can repair. The benchmarks the field trusts most are already carrying it. Ten widely used test sets were searched for mislabelled examples, and in 2021 Northcutt and colleagues reported what the search found: “Errors in test sets are numerous and widespread: we estimate an average of at least 3.3% errors across the 10 datasets, where for example label errors comprise at least 6% of the ImageNet validation set.” These are the test sets against which model rankings are declared.

The cause is frequently the ontology rather than the annotator. A re-annotation of the ImageNet validation set, published by Beyer and colleagues in 2020, found that roughly 29% of images either contain multiple objects or fall under a category matching several ImageNet synonym labels. For nearly a third of that set, a single forced label was never a description of the image. It was a choice among defensible answers, and the guideline had failed to make it in advance. Each question below is one of those choices, made once in the manual rather than silently and differently by every annotator.

  • Occlusion: Should a box cover the full inferred object, only visible pixels, or exclude heavily hidden instances?
  • Truncation: How should an object touching the image boundary be marked and evaluated?
  • Reflection: Is a person visible in a mirror a real instance for the product decision?
  • Group labels: Does a crowd receive one region, several instances, or an ignore zone?
  • Uncertain class: Can the annotator abstain, mark “other,” or request expert review?
  • Temporal identity: When does an object leaving and re-entering a scene keep the same track ID?

Disagreement can reveal an underspecified target

Annotators may disagree because an image is low quality, the ontology is unclear, or the underlying concept is genuinely subjective. Majority vote can hide those causes.

How much disagreement survives review is itself a measurement. When the algorithmically flagged label-error candidates went to crowd workers, only 51% were confirmed erroneous. Roughly half of the suspicious labels were defended by human reviewers rather than overturned. On ImageNet validation, around 29% of images contain multiple objects or match several synonym labels. That is a structural reason for two careful annotators to differ and for both of them to be correct.

Preserve raw judgments, confidence, and adjudication outcomes where feasible. Some applications should model ambiguity or use soft targets rather than force a false single truth.

Label uncertainty is often evidence about the task, not merely a nuisance to remove.

Analogy

A museum collection built through one doorway

Paintings reach a museum only if they are small enough to fit one narrow entrance, and a visitor judges world art from what hangs inside. The collection may be huge yet systematically exclude other forms.

A doorway is one physical opening. Dataset sampling is shaped by sensors, incentives, and workflows. Selection bias is what the two have in common.

Ask which deployment events never had a chance to enter the dataset.

Steps

Run annotation quality control without treating annotators as interchangeable

Quality control should diagnose policy, tooling, and evidence problems as well as individual mistakes. A review process that can only mark an annotator right or wrong will record ontology failures as personnel scores. Multi-object images, missing abstain options, undefined visibility rules — every one of them lands on somebody's record, and stays there.

FigureProcess · 5 steps
  1. 1. Pilot the ontology

    Annotate a diverse sample before committing to full-scale production.

  2. 2. Measure agreement by case type

    Separate easy, ambiguous, low-quality, and expert-only examples.

  3. 3. Review disagreements

    Classify causes such as unclear rules, tool friction, or genuine uncertainty.

  4. 4. Calibrate annotators

    Use examples with rationale and periodic blind checks, not only score penalties.

  5. 5. Version labels and policy

    Retain who changed what, when, why, and under which guideline revision.

Key idea

Legal access, ethical use, and technical provenance are different questions

A file being publicly reachable does not automatically grant suitable training rights. Consent for capture may also differ from consent for identity analysis, medical inference, or model release.

Two European regulators have put a price on that distinction. Both penalised Clearview AI for building a face-search database out of publicly reachable web images. The CNIL imposed a fine of €20,000,000 on 17 October 2022 and ordered deletion of French residents' data. The Dutch supervisory authority imposed €30,500,000 by a decision of 16 May 2024, announced on 3 September 2024, for processing without a legal basis under the GDPR. Public reachability was the collection method in both cases. In neither was it a defence.

Provenance failure also takes a form no licence review would catch. A scan of 32,138,129 items in the LAION datasets, published on 23 December 2023 by David Thiel of the Stanford Internet Observatory, found what no licence covers: “Through this process, we identified 3,226 dataset entries of suspected CSAM, much of which was confirmed as CSAM by third parties.” The scan produced 1,679 PhotoDNA matches. Of those, the 746 URLs still live were reviewed by the Canadian Centre for Child Protection and classified as CSAM or possible CSAM. LAION took LAION-5B offline. On 30 August 2024 it released Re-LAION-5B with 2,236 links removed, subsuming the 1,008 links the Stanford report had surfaced. The remediation was possible only because the corpus was a list of identifiable, individually removable references.

Record source, license, consent basis, permitted uses, retention, transformations, and downstream restrictions. Provenance supports both engineering and governance decisions.

An undocumented image is not a neutral training example.

Split by the dependency that could inflate generalization

Images from one video, patient, product unit, property, satellite pass, or camera site can be strongly correlated. Splitting individual frames at random may make recognizing the source look like task competence.

A chest radiograph turned out to be legible as a hospital. Zech and colleagues trained CNNs on 158,323 chest radiographs from three institutions, then asked the network to identify the source rather than the disease: “CNNs were able to directly detect hospital system of a radiograph for 99.95% NIH (22,050/22,062) and 99.98% MSH (8,386/8,388) radiographs.” The site was almost perfectly legible in the pixels. The consequence appeared when the boundary was moved. Pneumonia-detection AUC fell from 0.802 internally at MSH to 0.717 externally at NIH. That result was published in PLOS Medicine on 6 November 2018, and DeGrave and colleagues later found the same failure mode in COVID-19 chest radiograph models. It is not an idiosyncrasy of one hospital pair.

Choose group, temporal, geographic, device, or site boundaries that match the intended claim. Keep a final test set insulated from annotation-policy tuning.

Even a carefully rebuilt test set is contested evidence rather than settled ground. New CIFAR-10 and ImageNet test sets were constructed “by closely following the original dataset creation processes”, and the field was then measured on them: “We evaluate a broad range of models and find accuracy drops of 3% - 15% on CIFAR-10 and 11% - 14% on ImageNet.” Recht and colleagues read the gap as real: “the accuracy drops are not caused by adaptivity”. Not overfitting to a reused test set, then, but models failing on slightly harder images drawn the same way. An independent group tested that reading. Engstrom and colleagues showed part of the gap is an artefact of the replication procedure itself, leaving an estimated 3.6% ± 1.5% of the original 11.7% ± 1.0% ImageNet drop unaccounted for. How the boundary is drawn is not a preliminary to the measurement. It is a quantity that had to be measured in turn.

The test boundary should block the shortcut your deployment claim is supposed to survive.

Example

Artifacts a serious dataset release should contain

What the team writes down should let another team understand both the data and the limits of the claim — including the parts that later have to be withdrawn.

ImageNet's person subtree was audited category by category and the audit reported at FAccT 2020. Of its 2,832 categories, 1,593 were judged potentially offensive labels. Acting on that had a countable cost, and Yang and colleagues stated it in the paper: “The unsafe synsets are associated with 600,040 images in ImageNet. Removing them would leave 577,244 images in the safe synsets of the person subtree of ImageNet.” ImageNet's maintainers announced the removal of those synsets in a dated public update.

Enumerate the ontology, judge it category by category, count the affected images, publish the change with a date. That sequence is only available to a release that already recorded which categories exist, which images sit under each, and which version a published result was measured against. The artifacts below are what make a correction of that kind executable rather than merely desirable.

  • Dataset card describing purpose, population, capture process, known exclusions, and prohibited uses
  • Annotation manual with examples, edge cases, visibility rules, and adjudication policy
  • Split manifest with grouping logic and duplicate-detection procedure
  • Provenance table covering source, rights, consent, transformations, and retention
  • Quality report with disagreement, missingness, slice coverage, and unresolved uncertainties
  • Version history linking media changes, label changes, and evaluation comparability

Key takeaways