GDELT CloudGDELT Cloud
Connected Situation / Through 2026-10-06

North Korean Missile Activity and Detection Dispute

stories
4
events
2
entities
12
connections
4
Retained edition
Evidence so far on 2026-10-06 UTC · updated 2026-10-06 16:23 UTC · analysis as of 2026-10-06 00:25 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On 2026-10-05, North Korea launched a strategic missile from Wonsan, in the Event titled “North Korea launches strategic missile from Wonsan.” [cite?] “Kim Jong Un oversees strategic missile launch during North Korean military drill” reports Kim Jong Un’s oversight of the launch during a military drill. “North Korea touts AI-guided missile as impossible to evade” presents North Korea’s claim about the missile’s evasion capability. On 2026-10-05, South Korea denied Kim Yo-jong’s claim that it failed to detect North Korean missile launches, in the Event titled “South Korea denies Kim Yo-jong’s missile-detection claim.”

Footnotes[4][3][1][5][2]
Assessment

The Wonsan launch Event is linked to the drill story, which reports Kim Jong Un’s oversight; the AI-guidance Story has no linked Event, so its claim that the missile was impossible to evade is not independently established by that Event. South Korea’s denial establishes its rejection of Kim Yo-jong’s detection allegation, not whether South Korea detected the launches. Kim Yo-jong is the target of the denial Event, while Kim Jong Un is mentioned in the Stories but has no recorded participation in either Event.

Footnotes[4][3][1][5][2][7][6]

Explanation originally captured 2026-10-06 · Evidence through 2026-10-06 UTC · Source edition sed_5d6e500c0fd61ba3657558099fe7359d

What informs this explanation
  • Complete retained Story and Event membership
  • Daily reporting and coded-occurrence time steps
  • Event taxonomies, metrics, units, and denominators
  • Canonical Entities and recorded actor/target bindings
  • Typed reporting, membership, and incident edges
  • Changes against the preceding retained edition
  • Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative

Evidence in numbers

This retained edition
  • Scope

    A 2-day Situation represented by 2 coded Events carried across 4 member Stories.

  • Coded activity

    The coded activity is led by 016 · Deny Responsibility (1) and TE02 · Military Technology Event (1).

  • Prominent subjects

    Kim Yo Jong is prominent in the retained actor and relationship evidence.

  • Entity coverage

    12 canonical Entities are linked to this edition.

Metric coverage. 2 coded Events · 2 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3.5
min 3max 4
2 measured
Systemic importance0.15
min 0.1max 0.2
2 measured
Propagation potential0.32
min 0.26max 0.38
2 measured
Market sensitivity0.05
min 0.05max 0.05
2 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 7 scores, distributions & definitions

How the coder scored the full retained Event set

2 coded events — 2 CAMEO+ (1 political)

  • Significance · 20.24
    min 0.17max 0.31
  • Magnitude · 23.5
    min 3max 4
  • Systemic · 20.15
    min 0.1max 0.2
  • Propagation · 20.32
    min 0.26max 0.38
  • Market · 20.05
    min 0.05max 0.05
  • Goldstein · 10
    min 0max 0
  • Confidence · 20.7
    min 0.56max 0.83

Quad class over that 1 event · Verbal Cooperation 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 1 sit outside POLITICAL, where Goldstein and quad class are undefined.

Significance

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events

Magnitude

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across all 2 events — every one of them CAMEO+

Systemic

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events — every one of them CAMEO+

Propagation

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events — every one of them CAMEO+

Market

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events — every one of them CAMEO+

Goldstein

1 measured / 1 eligible · 0 missing · 1 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 1 of 2 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics

Confidence

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day2 reporting days · click a day to open or close it

2026-10-06from the recordslatest

North Korea launches hypersonic intermediate-range strategic missile

1 Story and 0 coded Events (-2 / -2 against the day before). Widest coverage: North Korea launches hypersonic intermediate-range strategic missile (1 articles).

1-2
Stories · vs day before
0-2
Events · vs day before
1
articles
The lay of the land

Situation timeline

Threads
All 2 daysarticlesstoriesevents
10-0510-06
Loading Situation timeline…

What kind of event · 2 coded types

over 2 coded events on this edition

  • Political1
    • 016 · Deny Responsibility1
  • Technology1
    • TE02 · Military Technology Event1
Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystMissile launch and capability claims

    The drill Story is linked to the Wonsan launch Event, while the AI-guidance Story reports a capability claim and is connected to the launch-related thread without an Event of its own.

    The drill Story is linked to the Wonsan launch Event, while the AI-guidance Story reports a capability claim and is connected to the launch-related thread without an Event of its own.

    Footnotes[3][4][1][9][10]
  2. development
    AnalystMissile-detection dispute

    The Seoul-denial Story reports South Korea’s rejection of Kim Yo-jong’s claim and is linked to the corresponding denial Event.

    The Seoul-denial Story reports South Korea’s rejection of Kim Yo-jong’s claim and is linked to the corresponding denial Event.

    Footnotes[2][5]

Key actors

  1. KJ
    AnalystKim Yo Jong

    Kim Yo-jong was the target of South Korea’s denial of her missile-detection claim.

    Kim Yo-jong was the target of South Korea’s denial of her missile-detection claim.

    Footnotes[7][5]

Key Events

  1. contextAnalystNorth Korea launches strategic missile from Wonsan

    The Event title identifies North Korea’s strategic missile launch from Wonsan on 2026-10-05.

    The Event title identifies North Korea’s strategic missile launch from Wonsan on 2026-10-05.

    Footnotes[4]
  2. contextAnalystSouth Korea denies Kim Yo-jong’s missile-detection claim

    On 2026-10-05, South Korea denied Kim Yo-jong’s missile-detection claim.

    On 2026-10-05, South Korea denied Kim Yo-jong’s missile-detection claim.

    Footnotes[5]

Notable connections

Evidenced relationships involving significant participants beyond the central cast.

  1. The Wonsan missile-launch Event is linked to the drill-and-oversight Story. · reporting linkAnalystNorth Korea launches strategic missile from Wonsan → Kim Jong Un oversees strategic missile launch during North Korean military drill

    The Event links to the Story reporting Kim Jong Un’s oversight of a strategic missile launch during a military drill.

    The Event links to the Story reporting Kim Jong Un’s oversight of a strategic missile launch during a military drill.

    Footnotes[4][3]
  2. The South Korea denial Event is linked to the Seoul-denial Story. · reporting linkAnalystSouth Korea denies Kim Yo-jong’s missile-detection claim → Seoul denies Kim Yo-jong’s claim that South Korea failed to detect North Korean missile launches

    The Event links South Korea’s denial of Kim Yo-jong’s claim to the Story about that denial.

    The Event links South Korea’s denial of Kim Yo-jong’s claim to the Story about that denial.

    Footnotes[5][2]
  3. Kim Yo-jong is the target of South Korea’s denial Event. · recorded participationAnalystKim Yo Jong → South Korea denies Kim Yo-jong’s missile-detection claim

    The Event identifies Kim Yo-jong as its target.

    The Event identifies Kim Yo-jong as its target.

    Footnotes[7][5]
  4. The AI-guidance Story and the drill Story are joined in the launch-related thread; that connection does not verify the.ғ · analytical connectionAnalystNorth Korea touts AI-guided missile as impossible to evade → Kim Jong Un oversees strategic missile launch during North Korean military drill

    The membership connection joins the capability report to the launch-related reporting, but does not independently establish the AI capability claim.

    The membership connection joins the capability report to the launch-related reporting, but does not independently establish the AI capability claim.

    Footnotes[9][10][1][3]
  5. The stories are marked as similar same-day coverage, not as reports of the same incident. · reporting linkAnalystSeoul denies Kim Yo-jong’s claim that South Korea failed to detect North Korean missile launches → North Korea touts AI-guided missile as impossible to evade

    The supplied edge marks the Seoul-denial and AI-guidance Stories as similar on the same day; it does not establish that they concern one incident.

    The supplied edge marks the Seoul-denial and AI-guidance Stories as similar on the same day; it does not establish that they concern one incident.

    Footnotes[11][2][1]
How a Situation is put together4 Stories · 2 Events · 4 membership connections · 28 graph edges

A retained time step

This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.

Stories, Events, and cast

Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 12 canonical people and organizations linked to the retained evidence.

Typed connections

Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.

Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.