Definition
Provenance is information about how a thing came to be. It records people, organizations, activities, source material, transformations, dates, rights, decisions and evidence. In a knowledge graph, provenance helps readers judge why a claim exists and how much trust to place in it.
Scope
Provenance includes authorship, publication, maintenance, derivation, citation, versioning, source custody and transformation history. It can apply to data, images, audio, code, publications, concepts and physical artefacts.
Why it matters
A knowledge system without provenance becomes a surface of claims. Provenance does not make every claim true, but it gives readers a path to evaluate reliability. It also helps future maintainers understand whether a record is original research, interpretation, migrated legacy material or external reference.
Electronic Artefacts position
Electronic Artefacts treats provenance as a public trust layer. A project, program or publication should expose authorship, publisher, modification date, confidence and sources. Relations should carry statements and confidence levels rather than acting as anonymous links.
Applications
Provenance is useful for archives, AI retrieval, digital preservation, cultural heritage, research reproducibility, software releases, dataset documentation and audio artefact interpretation.
Limitations
Provenance is not infinite documentation. A record can always explain more. The editorial task is to preserve enough lineage to support interpretation, rights, trust and future migration.
References
See W3C PROV, the Electronic Artefacts relation schema and the Digital Preservation concept.