Significance
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events
Connected Situation / Through 2026-11-13
Nasser Hospital Strike and Turkish Condemnation
- stories
- 5
- events
- 1
- entities
- 24
- connections
- 5
Evidence so far on 2026-11-13 UTC · updated 2026-11-13 12:34 UTC · analysis as of 2026-11-13 12:23 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On November 12, “Israeli strike on Nasser Hospital in southern Gaza kills five” reported that an Israeli strike on the hospital killed five people. On November 13, “Israel strikes Gaza's Nasser Hospital seven times, health officials say” attributed a report of seven strikes to health officials; this is a reported figure, not a separately coded strike event. “IDF says Hamas held hostages and ran a military headquarters at Nasser Hospital” attributes that account to the IDF, not to independent confirmation. On November 13, Numan Kurtulmuş condemned Israel over the hospital attack in a coded political event linked to “Türkiye condemns Israeli hospital strike in Gaza as illegal.” “Turkey condemns Israeli strike on Nasser Hospital in Gaza” also covered Turkey’s condemnation. The two condemnation stories describe political reactions to the same hospital strike, while the IDF account and the health officials’ reported figure add distinct, attributed claims about the incident.
Footnotes[5][4][3][6][1][2][9][10][11][12]Assessment
The central supported account is an Israeli strike on Nasser Hospital, reported on November 12 as having killed five; the later report of seven strikes is attributed to health officials and does not establish seven separate events. The IDF’s account that Hamas held hostages and operated a military headquarters at the hospital remains an attributed claim, not independent confirmation. The clearest coded action on November 13 is Numan Kurtulmuş’s condemnation of Israel, and the two Turkish-condemnation stories are linked to that same incident rather than establishing additional attacks. These materials establish the attack as the subject of the accounts and the political condemnation; they do not independently establish the IDF’s account or resolve the difference between the reported strike descriptions.
Footnotes[5][4][3][6][1][2][9][10][11][12]As-of explanation captured 2026-11-13 · Evidence through 2026-11-13 UTC
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 1 coded Event carried across 5 member Stories.
- Coded activity
The coded activity is led by 111 · Criticize or Denounce (1).
- Prominent subjects
🇹🇷Turkey is prominent in the retained actor and relationship evidence.
- Entity coverage
24 canonical Entities are linked to this edition.
Metric coverage. 1 coded Events · 1 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude4
min 4max 4
Systemic importance0.1
min 0.1max 0.1
Propagation potential0.36
min 0.36max 0.36
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
1 coded event — 1 CAMEO+ (1 political)
- Significance · 10.26min 0.26max 0.26
- Magnitude · 14min 4max 4
- Systemic · 10.1min 0.1max 0.1
- Propagation · 10.36min 0.36max 0.36
- Market · 10.05min 0.05max 0.05
- Goldstein · 1-2min -2max -2
- Confidence · 10.86min 0.86max 0.86
Quad class over that 1 event · Verbal Conflict 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero.
Magnitude
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Systemic
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Propagation
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Market
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Goldstein
1 measured / 1 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 1 of 1 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Confidence
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 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-11-13analystlatest
Further accounts and political condemnation
Stories published on this date attribute a seven-strike figure to health officials and an account of Hamas at the hospital to the IDF; the coded Event on this date is Numan Kurtulmuş’s condemnation of Israel. These accounts add attributed detail and a political reaction to the hospital-strike coverage.
- 4+3
- Stories · vs day before
- 1+1
- Events · vs day before
- 10
- articles
The lay of the land
Situation timeline
Threads
All 2 daysarticlesstoriesevents
11-1211-13
Loading Situation timeline…
What kind of event · 1 coded type
over 1 coded event on this edition
- Political1
- 111 · Criticize or Denounce1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystNasser Hospital strike and competing accounts
The November 12 report of five deaths is joined to the later health officials’ report of seven strikes and the IDF’s attributed account of Hamas at the hospital; the latter stories are treated as details or context for the same incident, not separate coded events.
- development
AnalystTurkish condemnation of the hospital strike
Both November 13 condemnation stories describe Turkey’s political reaction to the Nasser Hospital strike; one is linked to the coded condemnation event.
Key actors
Key Events
responseAnalystNuman Kurtulmuş condemns Israel over Nasser Hospital attack
On November 13, Numan Kurtulmuş condemned Israel over the Nasser Hospital attack; the linked story and incident connections identify the condemnation as a political reaction to the strike.
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The story is linked to Numan Kurtulmuş’s condemnation of Israel over the hospital attack. · reporting linkAnalystNuman Kurtulmuş condemns Israel over Nasser Hospital attack → Türkiye condemns Israeli hospital strike in Gaza as illegal
The Event names this Story as its supporting story.
Turkey’s condemnation is connected to the Nasser Hospital strike described in the earlier story. · analytical connectionAnalystTurkey condemns Israeli strike on Nasser Hospital in Gaza → Israeli strike on Nasser Hospital in southern Gaza kills five
The supplied connection identifies the condemnation as a reaction to the strike.
Türkiye’s condemnation is connected to the Nasser Hospital strike described in the earlier story. · analytical connectionAnalystTürkiye condemns Israeli hospital strike in Gaza as illegal → Israeli strike on Nasser Hospital in southern Gaza kills five
The supplied connection identifies the condemnation as a political reaction to the strike.
How a Situation is put together5 Stories · 1 Events · 5 membership connections · 41 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 24 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.