Record entry · Japan

Typhoon Dujuan

Added 6 Oct 2026Mentions 22Sources 8Days of coverage 10

Why this name is on the record

Typhoon Dujuan was added automatically on 6 Oct 2026 after 22 mentions across 8 sources over 10 days. 50% of that coverage came from a single subject area.

Who Typhoon Dujuan moves with

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.

JapanTokyoIceland
  • Japan · 22 shared documents
  • Tokyo · 20 shared documents
  • Chiba · 12 shared documents · no page of its own yet
  • Kanto · 10 shared documents · no page of its own yet
  • Chiba Prefecture · 9 shared documents · no page of its own yet
  • Iceland · 9 shared documents
  • Kanagawa · 8 shared documents · no page of its own yet

For developers

GET https://sigb.ai/api/registry?slug=typhoon-dujuan

{
  "slug": "typhoon-dujuan",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "typhoon dujuan",
    "promotedAt": "2026-10-06",
    "category": "japan",
    "evidence": {
      "mentions": 22,
      "sources": 8,
      "days": 10,
      "concentration": 0.5,
      "standAloneShare": 0.909
    }
  }
}

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

Walk the record from Typhoon Dujuan

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.

Typhoon Dujuan

Entity.

Evidence
23 documents · 9 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 20 Sept 2026, last seen 5 Oct 2026
Measured
56% of mentions say something specific about it; the rest only name it
As of
6 Oct 2026
7 links from here

Who it moves with: the 7 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