Significance
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events
Connected Situation / Through 2026-10-24
Tibet Earthquake and Responses
- stories
- 6
- events
- 5
- entities
- 34
- connections
- 6
Evidence so far on 2026-10-24 UTC · updated 2026-10-24 11:22 UTC · analysis as of 2026-10-24 08:29 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 23 October 2026, “Magnitude 7 earthquake in Tibet kills 16 and injures dozens, China reports” reported 16 deaths and dozens injured, attributing the figures to China. “Magnitude 7.0 earthquake strikes Drachen County in Tibet” describes the same magnitude-7 earthquake and adds Drachen County as a location detail. On 23 October, China’s Ministry of Emergency Management made a public statement; the Event title characterizes it as raising the disaster-response level, while its description says only “Make public statement.” “Vietnamese leaders express sympathy after serious earthquake in Tibet” reports expressions of sympathy that the connection identifies as a response to the earthquake. Xi Jinping, Trần Thanh Mẫn, Tô Lâm and Lê Minh Hưng are mentioned in the related Stories, but their Entity entries show no supporting Events.
Footnotes[1][3][12][4][2][11][5][6][7][9]Assessment
The earthquake and reported human toll are the core; the Drachen County headline is linked as a location-detail variant, not a separate incident. The 16 deaths and dozens injured remain figures reported in the earthquake headline, while the ministry Event describes a public statement and supplies no casualty counts; its confidence is 0.38. The Vietnamese leaders’ expressions of sympathy are linked as a response, but the named people’s mention-only Entity entries do not establish participation in the coded Event or further actions by them.
Footnotes[1][3][12][4][11][2][5][6][7][9]Explanation originally captured 2026-10-24 · Evidence through 2026-10-24 UTC · Source edition sed_6a12bd583d2c6764c6a21b4261643f45
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
- Scope
A 2-day Situation represented by 5 coded Events carried across 6 member Stories.
- Coded activity
The coded activity is led by EN01 · Geophysical Hazard (2) and 01 · Make Public Statement (1).
- Prominent subjects
🇨🇳China is prominent in the retained actor and relationship evidence.
- Entity coverage
34 canonical Entities are linked to this edition.
Metric coverage. 5 coded Events · 5 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude1.6
min 1max 3
Systemic importance0.08
min 0.05max 0.1
Propagation potential0.28
min 0.25max 0.34
Market sensitivity0.05
min 0.05max 0.05
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
5 coded events — 5 CAMEO+ (2 political)
- Significance · 50.21min 0.13max 0.31
- Magnitude · 51.6min 1max 3
- Systemic · 50.08min 0.05max 0.1
- Propagation · 50.28min 0.25max 0.34
- Market · 50.05min 0.05max 0.05
- Goldstein · 23.7min 0max 7.4
- Confidence · 50.41min 0.34max 0.55
Quad class over those 2 events · Material Cooperation 1 · Verbal Cooperation 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 3 sit outside POLITICAL, where Goldstein and quad class are undefined.
Magnitude
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 5 events — every one of them CAMEO+
Systemic
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events — every one of them CAMEO+
Propagation
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events — every one of them CAMEO+
Market
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events — every one of them CAMEO+
Goldstein
2 measured / 2 eligible · 0 missing · 3 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 2 of 5 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Confidence
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events
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-24from the recordslatest
China National Petroleum sets up emergency fuel point in Baqing
3 Stories and 3 coded Events (0 / +1 against the day before). Widest coverage: Magnitude 7 earthquake strikes Tibet in China, killing 16 (26 articles).
- 30
- Stories · vs day before
- 3+1
- Events · vs day before
- 28
- articles
The lay of the land
Situation timeline
Threads
All 2 daysarticlesstoriesevents
10-2310-24
Loading Situation timeline…
What kind of event · 4 coded types
over 5 coded events on this edition
- Environment2
- EN01 · Geophysical Hazard2
- Political2
- 01 · Make Public Statement1
- 073 · Provide Humanitarian Aid1
- Infrastructure1
- IN01 · Energy Infrastructure Event1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystEarthquake and reported impact
The main headline reports deaths and injuries; the Drachen County Story is linked as a same-incident location-detail variant.
- development
AnalystResponses associated with the earthquake
The earthquake account links to a ministry public-statement Event, and the sympathy Story is linked as a response to the earthquake.
Key actors
Key Events
contextAnalystChina's Ministry of Emergency Management raises disaster response level
On 23 October 2026, China’s Ministry of Emergency Management made a public statement; the target is unspecified.
On 23 October 2026, China’s Ministry of Emergency Management made a public statement; the target is unspecified.
Footnotes[4]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
is linked to the ministry's public-statement Event · reporting linkAnalystMagnitude 7 earthquake in Tibet kills 16 and injures dozens, China reports → China's Ministry of Emergency Management raises disaster response level
The Event lists the earthquake account as its supporting Story.
describes the same magnitude-7 earthquake, with Drachen County as a location detail · analytical connectionAnalystMagnitude 7 earthquake in Tibet kills 16 and injures dozens, China reports → Magnitude 7.0 earthquake strikes Drachen County in Tibet
The Stories are linked as accounts of the same incident.
reports sympathy as a response to the earthquake · analytical connectionAnalystVietnamese leaders express sympathy after serious earthquake in Tibet → Magnitude 7 earthquake in Tibet kills 16 and injures dozens, China reports
The connection identifies the Vietnamese leaders’ expressions of sympathy as a response to the earthquake.
is mentioned in the earthquake account; the Entity entry does not bind it as an Event participant · reporting linkAnalystMinistry of Emergency Management of the People's Republic of China → Magnitude 7 earthquake in Tibet kills 16 and injures dozens, China reports
The Ministry of Emergency Management Entity is listed as a mention in this Story and has no supporting Events.
How a Situation is put together6 Stories · 5 Events · 6 membership connections · 49 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 34 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.