Record entry · South Korea

Suwon

What is happening now

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

How well we know this

154 documents · 10 publishers · 0% say something specific about it · last evidence 10 Nov 2026

  • Gap: 0% of mentions say something specific about it; the rest only name it
Added 17 Oct 2026Mentions 36Sources 6Days of coverage 24

Why this name is on the record

Suwon was added automatically on 17 Oct 2026 after 36 mentions across 6 sources over 24 days. 97% of that coverage came from a single subject area.

Reported alongside Suwon

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.

SeoulSouth KoreaGyeonggi Provin…LionsSamsung Electro…HyunKorea Baseball …

For developers

GET https://api.signalbureau.ai/api/registry?slug=suwon

{
  "slug": "suwon",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "suwon",
    "promotedAt": "2026-10-17",
    "category": "south_korea",
    "evidence": {
      "mentions": 36,
      "sources": 6,
      "days": 24,
      "concentration": 0.972,
      "standAloneShare": 0.591
    }
  }
}

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

Walk the record from Suwon

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.

Suwon

Entity.

Evidence
154 documents · 10 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
A name from our starting list; its record is kept up to date automatically from coverage
Time
first seen 3 Sept 2026, last seen 10 Nov 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
10 Nov 2026
10 links from here

Who it moves with: the 10 names are in the map above.

What is claimed about it (0)

none on file at this cutoff

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this