Training data
Also known as: training set
The examples a model learns from; its behaviour, its blind spots and its mistakes all come from what is in them.
Draft - this entry has not been reviewed yet.
Formal
The collection of examples, often with the correct answers attached, used during model training to set a model's internal numbers; kept apart from the data later used to test it.
In plain English
Like the textbooks and past exams a student studies from. If they are wrong, one-sided or out of date, so is what the student learns.
In practice
A pension fund wants to train a model on ten years of member emails and must first check which of them hold personal data and on what legal basis they may be used.
Technical deep dive
Standard practice splits available data into three disjoint sets: the training set used to fit weights, a validation set used to choose hyperparameters and stopping points, and a test set touched once for the final estimate. Splits must respect the structure of the data: grouped splits keep all records from one patient or customer on one side, and time-based splits train on the past and test on the future. Violating this causes leakage and optimistic scores. For large language models the analogous problem is benchmark contamination, where test items appear in the web-scale pretraining corpus, so reported benchmark results partly measure memorisation.
Quality problems are well characterised. Label noise from annotators is estimated with inter-annotator agreement statistics such as Cohen's kappa; sampling bias arises when collection differs from deployment (a model trained on one hospital's scanners); historical bias arises when accurate labels encode past discrimination; and class imbalance means rare, often important cases are underrepresented. Deduplication matters at scale: duplicated sequences in web corpora increase memorisation and the chance that a model reproduces personal data verbatim.
Training data is an attack surface. Data poisoning inserts crafted examples so the model misbehaves in general or only on a trigger (a backdoor). Web-scraped corpora are exposed because an attacker can control content at URLs that will be crawled. Provenance tracking, dataset hashes, access control on labelling pipelines and anomaly checks on new data are the corresponding controls, alongside documentation such as datasheets for datasets.
The legal framework in Europe is layered. Personal data in a training set needs a legal basis under GDPR Article 6, and special categories under Article 9; purpose limitation and data minimisation apply to training as to any processing. For high-risk systems, Article 10 of the EU AI Act requires data governance practices covering design choices, collection, preparation, and examination for possible biases, and Article 10(3) requires training, validation and testing data sets to be relevant, sufficiently representative and, to the best extent possible, free of errors and complete in view of the intended purpose. Article 10(5) allows exceptional processing of special-category data strictly for bias detection and correction, under safeguards. Providers of general-purpose AI models must publish a sufficiently detailed summary of training content (Article 53(1)(d)) and have a policy to comply with EU copyright law (Article 53(1)(c)), including machine-readable opt-outs from text and data mining under Article 4(3) of the DSM Directive (EU) 2019/790.
Relationships
- A kind of
- Asset
- Kinds
- Synthetic data
- Consists of
- Label
- Unlocks
- AI biasClusteringCross-validationData driftData labelingEpochFeatureKnowledge cutoffMachine learningModel cardModel trainingOverfittingPretrainingSelf-supervised learningSensitive information disclosureSupervised learningUnsupervised learning
- Don't confuse with
- Validation setContext windowTest set
- Exploited by
- Data poisoning
- Causes
- AI bias
Sources & further reading
Standards & official texts
- ISO/IEC 22989:2022, Information technology: Artificial intelligence concepts and terminology · ISO/IEC
- Regulation (EU) 2024/1689 (Artificial Intelligence Act), Article 10 (Data and data governance) and Article 53 · European Union
- NIST AI 100-1 (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0) · NIST
- Regulation (EU) 2016/679 (GDPR), Articles 6 and 9 · European Union
Where this data comes from
This entry was drafted by an AI from the sources above and has not yet been checked by a person. Treat it as a starting point, and check anything important against the sources.
See the review queueSuggest a correction on GitHubThis term as JSON
Mentioned in
Check yourself
Loading…