Record entry · Disaster

South Fork

What is happening now

Nothing reported: the record holds no registered event and no claim that names this.

How well we know this

29 documents · 15 publishers · 0% contain a typed assertion · last evidence 24 Oct 2026

Gap: assertion coverage 0: about 100% of mentions carry no typed assertion

Added 25 Oct 2026Mentions 20Sources 10Days of coverage 16

Why this name is on the record

South Fork was added automatically on 25 Oct 2026 after 20 mentions across 10 sources over 16 days. 55% of that coverage came from a single subject area.

Reported alongside South Fork

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

Pueblo · 10 shared documents · no page of its own yet
Flash Flood Warnings · 9 shared documents · no page of its own yet
Puerto Rico · 9 shared documents · no page of its own yet

For developers

GET https://api.signalbureau.ai/api/registry?slug=south-fork

{
  "slug": "south-fork",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "south fork",
    "promotedAt": "2026-10-25",
    "category": "disaster",
    "evidence": {
      "mentions": 20,
      "sources": 10,
      "days": 16,
      "concentration": 0.55,
      "standAloneShare": 0.519
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from South Fork

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

South Fork

Entity.

Evidence: 29 documents · 15 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing: Added automatically from coverage
Time: first seen 8 Sept 2026, last seen 24 Oct 2026
Measured: 0% of mentions say something specific about it; the rest only name it
As of: 25 Oct 2026