Skip to main content
A model is a resource. A dataset is a resource. Training is an action that consumes datasets and produces a model. This pattern records the full chain natively in the EAA graph.
EU AI Act Art. 53(1)(d) requires providers of general-purpose AI models to maintain a “sufficiently detailed summary” of training data. Art. 53(1)(c) requires that models comply with copyright law, including DSM Art. 4 text-and-data-mining opt-outs. ProvenanceKit records this natively — no special AI-specific schema required.

The Pattern

Every node in this graph is an EAA record. The training action records exactly which datasets were consumed and which model was produced.

Recording the Pattern

Querying the Training Provenance

Generating an EU AI Act Summary

Checking Dataset Opt-Out Status Before Training

Incremental Training and Fine-Tuning

For fine-tuning (model → fine-tuned model):

Gotchas

  • Large dataset files: Don’t upload raw multi-GB datasets to IPFS via ProvenanceKit. Upload a manifest file (JSON listing dataset shards, checksums, source URLs) and pin that. The CID of the manifest is what goes in the provenance graph.
  • Existing datasets: For well-known public datasets (Common Crawl, The Pile, etc.), use their known CIDs if published, or create a resource with cid: "external:commonCrawl-2024-10" and document the reference in metadata.
  • Model weights on IPFS: Safetensors / GGUF files can be hundreds of GB. Same as datasets — upload a model card (JSON) and pin that. The actual weights can live on HuggingFace Hub with the HuggingFace URL recorded in metadata.