Record entry · Japan

Self Defense Forces

What is happening now

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

How well we know this

31 documents · 11 publishers · 0% contain a typed assertion · last evidence 25 Oct 2026

  • Gap: assertion coverage 0: about 100% of mentions carry no typed assertion
Added 26 Oct 2026Mentions 20Sources 6Days of coverage 17

Why this name is on the record

Self Defense Forces was added automatically on 26 Oct 2026 after 20 mentions across 6 sources over 17 days. 75% of that coverage came from a single subject area.

Reported alongside Self Defense Forces

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.

JapanIcelandTokyoUnited States

For developers

GET https://api.signalbureau.ai/api/registry?slug=self-defense-forces

{
  "slug": "self-defense-forces",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "self-defense forces",
    "promotedAt": "2026-10-26",
    "category": "japan",
    "evidence": {
      "mentions": 20,
      "sources": 6,
      "days": 17,
      "concentration": 0.75,
      "standAloneShare": 0.581
    }
  }
}

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

Walk the record from Self Defense Forces

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.

Self-Defense Forces

Entity.

Evidence
31 documents · 11 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 3 Sept 2026, last seen 25 Oct 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
26 Oct 2026
4 links from here

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