Skip to content

AI Glossary · Concepts

What is Training, Validation and Test Sets?

Training, Validation and Test Sets

Training, validation and test sets are three non-overlapping slices of a dataset. The model learns from the training set, people use the validation set to compare versions and tune settings, and the test set is held back for one final, honest check on data the model has never influenced.

Also known as: training set, validation set, test set, holdout set, train/validation/test split, train-test split, dev set

· Chain of Thought

Model TrainingAI Evaluation & Reliability

  • 1 explainer
  • 3 episodes
  • 1 guest clip
  • 2 sources

A teacher who hands out the final exam as homework learns nothing from the exam scores. Machine learning has the same problem, so teams split their dataset before training. A common split is something like 80% training, 10% validation and 10% test, though the right sizes depend on how much data exists.

Each slice has one job. The training set is what the model fits its parameters to. The validation set (also called a dev set) is what people check during development: which version is better, which hyperparameter setting wins, when to stop training before overfitting sets in. The test set is opened at the end to estimate how the chosen model will do on genuinely new data. Google’s course warns that validation and test sets “wear out”: every time a team peeks at test results and adjusts, the test set becomes a little more like training data and the score becomes a little less trustworthy. Cross-validation is a way to get more out of limited data during the validation stage.

The split only works if information can’t cross it. Duplicates, near-duplicates or the same customer appearing in both training and test is a form of data leakage, and for time-ordered data the test set should come from later dates. The same idea carries into LLM evaluation: an eval set kept out of prompts and fine-tuning data, and public benchmarks that may have leaked into pre-training data (benchmark contamination).

In episode 34 at 41:24, Corti CEO Andreas Cleve says building clinical AI takes many datasets and “a lot of holdouts,” then checks the output inside the doctor’s workflow, where a doctor’s sign-off acts as a further label. That is his account of Corti’s process. The episode was sponsored by Galileo, where Conor worked at the time (33:48).

Hear it from the guest

“So we do we do need a lot of data sets. We need a lot of holdouts”

Quotes lightly edited to remove filler words.

Sources

Go deeper

From the conversation