Skip to content

#provenance-ledger

12 approved public terms with this tag.

Dataset Provenance Ledger is a ml record that tracks where data came from and how it changed for labeled and unlabeled data used for learning. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Dataset Provenance Ledger when the dataset received a new batch, so the team could audit model inputs reliably before the model moved into evaluation.

Embedding Provenance Ledger is a ml record that tracks where data came from and how it changed for vector representation of content or entities. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Embedding Provenance Ledger when the embedding index changed, so the team could audit model inputs reliably before the model moved into evaluation.

Experiment Provenance Ledger is a ml record that tracks where data came from and how it changed for controlled model comparison. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Experiment Provenance Ledger when the experiment showed a metric tradeoff, so the team could audit model inputs reliably before the model moved into evaluation.

Feature Provenance Ledger is a ml record that tracks where data came from and how it changed for input signals used by a machine learning model. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Feature Provenance Ledger when a feature distribution shifted, so the team could audit model inputs reliably before the model moved into evaluation.

Fine-Tuning Provenance Ledger is a ml record that tracks where data came from and how it changed for adaptation of a model to a domain. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Fine-Tuning Provenance Ledger when the fine-tuning run used curated examples, so the team could audit model inputs reliably before the model moved into evaluation.

Inference Provenance Ledger is a ml record that tracks where data came from and how it changed for model prediction serving. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Inference Provenance Ledger when the endpoint handled burst traffic, so the team could audit model inputs reliably before the model moved into evaluation.

Label Provenance Ledger is a ml record that tracks where data came from and how it changed for ground-truth or weak-supervision annotation. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Label Provenance Ledger when the label set had disagreement, so the team could audit model inputs reliably before the model moved into evaluation.

Metric Provenance Ledger is a ml record that tracks where data came from and how it changed for measurement of model behavior. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Metric Provenance Ledger when the metric changed after data cleanup, so the team could audit model inputs reliably before the model moved into evaluation.

Model Drift Provenance Ledger is a ml record that tracks where data came from and how it changed for changes in model performance over time. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Model Drift Provenance Ledger when the live population changed, so the team could audit model inputs reliably before the model moved into evaluation.

Pipeline Provenance Ledger is a ml record that tracks where data came from and how it changed for automated data and model workflow. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Pipeline Provenance Ledger when the pipeline missed a validation step, so the team could audit model inputs reliably before the model moved into evaluation.

Training Provenance Ledger is a ml record that tracks where data came from and how it changed for model learning and optimization workflows. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Training Provenance Ledger when the training job restarted, so the team could audit model inputs reliably before the model moved into evaluation.

Vector Provenance Ledger is a ml record that tracks where data came from and how it changed for numeric representation and similarity search. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

The machine learning team used Vector Provenance Ledger when the vector store returned close matches, so the team could audit model inputs reliably before the model moved into evaluation.