Attach sources, attribution, and qualifications to individual graph statements.
A fact can need more than a value: who supplied it, what supports it, and which qualifications apply. Attach that context to the individual statement rather than leaving readers to infer it from an entire document.
Keep an assessor's claim distinguishable from an accepted fact. Multiple sources can discuss the same statement without becoming one source or implying agreement.
Provenance explains the wider chain of derivation and attribution.
Developer reference
RDF 1.2 defines triple terms that represent subject, predicate, and object together. A reifier links to that term through rdf:reifies; metadata then describes the reifier. Reifying a triple does not assert that triple.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix ex: <https://example.org/> .
ex:claim a prov:Entity ;
rdf:reifies <<( ex:prospect ex:eligible true )>> ;
prov:wasAttributedTo ex:assessor .
This uses PROV-O attribution alongside RDF reification. Applications can query the claim's evidence without treating ex:eligible true as an asserted conclusion. RDF 1.2 is a W3C Candidate Recommendation; that maturity level matters when choosing interoperable tooling.
A source IRI or attribution statement is data, not a signature check. Cryptographic integrity proves a record's relationship to committed content; deciding whether the assessor is trusted requires an explicit policy. Store those distinctions rather than equating recorded evidence with verified truth.