Semi-Supervised Learning

Semi-supervised learning uses a small labeled set together with a larger unlabeled or weakly labeled set. It is useful when labels are expensive, incomplete, noisy, or selectively observed.

Let:

be labeled data and:

be unlabeled data. A common objective combines supervised and unsupervised terms:

where controls the strength of the unlabeled-data objective.

Common Signals

  • Pseudo-labeling: use a model prediction as a temporary label.
  • Consistency regularization: predictions should remain stable under augmentation.
  • Teacher-student training: use a teacher model or moving average model to guide the student.
  • Graph or nearest-neighbor propagation: spread labels through similarity structure.
  • Weak-label bootstrapping: combine heuristic labels with cleaner held-out evaluation labels.

Pseudo-Labeling

For a model distribution , a pseudo-label can be:

Often only high-confidence predictions are used:

where is a confidence threshold selected without using the final test set.

Consistency Regularization

Consistency methods ask predictions to be stable under perturbations:

where are augmentations and is a divergence or distance.

This only helps if augmentations preserve the label. In molecular, protein, or scientific data, augmentation validity must be domain-aware.

Data Contract

Semi-supervised learning should keep label sources separate.

SetContainsUse
clean labeledhuman/assay/verified labelssupervised loss and validation/test
unlabeledinputs without labelsconsistency, pseudo-labeling, pretraining
weak labeledheuristic/noisy labelsauxiliary signal
pseudo-labeledmodel-generated labelstraining only, not final truth

Do not merge these into one label column without a label-source field.

Failure Modes

FailureSymptom
confirmation biaspseudo-label errors become stronger over training
threshold biasonly easy examples enter pseudo-label set
distribution mismatchunlabeled pool changes representation in wrong direction
false negative poolunknown positives treated as unlabeled negatives
evaluation contaminationunlabeled pool contains test near-duplicates

Risks

  • Confirmation bias: the model reinforces its own wrong predictions.
  • Hidden label noise: weak labels are treated as clean labels.
  • Sampling bias: unlabeled data comes from a different distribution.
  • Leakage: unlabeled data includes near-duplicates or future test examples.
  • Evaluation mismatch: final claims use weak labels instead of clean labels.

Checks

  • Which data are labeled, unlabeled, weakly labeled, or pseudo-labeled?
  • Is the unlabeled pool from the same target distribution as deployment?
  • Are pseudo-label thresholds selected on validation data?
  • Is final evaluation done on clean labels?
  • Are weak negatives separated from true negatives?
  • Can the method leak information through duplicate unlabeled examples?
  • Is label source preserved in the schema?
  • Are pseudo-labels evaluated against clean labels before being trusted?