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

Poland: Alleged Plot Targeting Donald Tusk

stories
4
events
2
entities
31
connections
4
Retained edition
Evidence so far on 2026-10-13 UTC · updated 2026-10-13 08:26 UTC · analysis as of 2026-10-13 05:32 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On October 11, Polish police warned of a possible attack targeting Prime Minister Donald Tusk in “Polish police warn of possible attack targeting Prime Minister Donald Tusk.” On that same coded occurrence date, Polish police arrested a man suspected of plotting an attack on Tusk, and a Polish government spokesperson said the suspected plot was being taken seriously. The October 12 headline “Poland foils alleged assassination plot targeting Prime Minister Donald Tusk” reports the follow-up on the alleged plot and is linked to the arrest Event, which is dated October 11. Also on October 12, “Polish President Duda downplays assassination threats, saying he was threatened daily” reports Andrzej Duda’s remarks; the link between that Story and the Tusk follow-up is a membership connection, not proof that Duda was addressing this specific alleged plot.

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

The Events establish an arrest of a man suspected of plotting an attack and a public statement that the suspected plot was taken seriously; they do not establish the suspect’s guilt or independently resolve the alleged plot. The arrest Event reports zero fatalities with the basis “none reported,” which is not a broader finding about the alleged plot. October 12 is a reporting date for the follow-up and Duda Stories, not the date of another coded Event in this Situation.

Footnotes[4][5][9][1][2]

Explanation originally captured 2026-10-13 · Evidence through 2026-10-13 UTC · Source edition sed_9329c9958d3a2466b6ff49bad884a77c

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 3-day Situation represented by 2 coded Events carried across 4 member Stories.

  • Coded activity

    The coded activity is led by 01 · Make Public Statement (1) and ARRESTS (1).

  • Prominent subjects

    🇵🇱Poland is prominent in the retained actor and relationship evidence.

  • Entity coverage

    31 canonical Entities are linked to this edition.

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

Magnitude3
min 3max 3
1 measured
Systemic importance0.1
min 0.1max 0.1
1 measured
Propagation potential0.26
min 0.26max 0.26
1 measured
Market sensitivity0.05
min 0.05max 0.05
1 measured

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

All 8 scores, distributions & definitions

How the coder scored the full retained Event set

2 coded events — 1 CAMEO+ (1 political) · 1 conflict

  • Significance · 20.21
    min 0.2max 0.21
  • Magnitude · 13
    min 3max 3
  • Systemic · 10.1
    min 0.1max 0.1
  • Propagation · 10.26
    min 0.26max 0.26
  • Market · 10.05
    min 0.05max 0.05
  • Goldstein · 2-2.5
    min -5max 0
  • Fatalities · 10
    min 0max 0
  • Confidence · 20.69
    min 0.56max 0.82

Quad class over those 2 events · Material Conflict 1 · Verbal Cooperation 1. The four CAMEO+ scores are over the 1 CAMEO+ events only; the 1 conflict events have no such column.

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

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

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

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

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

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

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

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

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

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Market

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

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

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

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

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

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

Fatalities

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

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 1 of 2 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

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 day3 reporting days · click a day to open or close it

2026-10-13from the recordslatest

Polish police arrest man over reported plot targeting Tusk and defense minister

1 Story and 0 coded Events (-1 / 0 against the day before). Widest coverage: Polish police arrest man over reported plot targeting Tusk and defense minister (2 articles).

Polish police arrest man over reported plot targeting Tusk and defense minister
1-1
Stories · vs day before
00
Events · vs day before
2
articles
The lay of the land

Situation timeline

Threads
All 3 daysarticlesstoriesevents
10-1110-1210-13
Loading Situation timeline…

What kind of event · 2 coded types

over 2 coded events on this edition

  • Conflict1
    • ARRESTS1
  • Political1
    • 01 · Make Public Statement1

Countries · where it happened

Countries · who is acting

Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystWarning, arrest and follow-up on the alleged plot

    The October 11 warning Story and October 12 follow-up Story are linked as precursor and continuation; that link does not independently establish causation.

    The October 11 warning Story and October 12 follow-up Story are linked as precursor and continuation; that link does not independently establish causation.

    Footnotes[11][12]
  2. development
    AnalystAndrzej Duda’s remarks on threats

    The membership connection links Duda’s October 12 Story to the Tusk follow-up as a consequence, but does not establish that the alleged plot caused his remarks.

    The membership connection links Duda’s October 12 Story to the Tusk follow-up as a consequence, but does not establish that the alleged plot caused his remarks.

    Footnotes[10][2][1]

Key actors

    Key Events

    1. contextAnalystPolish police arrest man suspected of plotting attack on Donald Tusk

      Dated October 11, this Event says Polish police arrested a man suspected of plotting an attack on Donald Tusk.

      Dated October 11, this Event says Polish police arrested a man suspected of plotting an attack on Donald Tusk.

      Footnotes[4]
    2. contextAnalystPolish government says it takes suspected Tusk plot seriously

      Dated October 11, this Event describes a Polish government spokesperson making a public statement that the government took the suspected Tusk plot seriously.

      Dated October 11, this Event describes a Polish government spokesperson making a public statement that the government took the suspected Tusk plot seriously.

      Footnotes[5]

    Notable connections

    Evidenced relationships involving significant participants beyond the central cast.

    1. supports the Event describing the government spokesperson’s statement · reporting linkAnalystPolish police warn of possible attack targeting Prime Minister Donald Tusk → Polish government says it takes suspected Tusk plot seriously

      The Event names this Story as its supporting Story.

      The Event names this Story as its supporting Story.

      Footnotes[5][3]
    2. supports the Event describing the arrest · reporting linkAnalystPoland foils alleged assassination plot targeting Prime Minister Donald Tusk → Polish police arrest man suspected of plotting attack on Donald Tusk

      The Event names this Story as its supporting Story.

      The Event names this Story as its supporting Story.

      Footnotes[4][1]
    3. linked as precursor and continuation · reporting linkAnalystPolish police warn of possible attack targeting Prime Minister Donald Tusk → Poland foils alleged assassination plot targeting Prime Minister Donald Tusk

      The Story edge labels the October 11 warning a precursor to the October 12 follow-up; that label does not independently establish causation.

      The Story edge labels the October 11 warning a precursor to the October 12 follow-up; that label does not independently establish causation.

      Footnotes[11][12][3][1]
    4. linked as a consequence in Situation membership · reporting linkAnalystPolish President Duda downplays assassination threats, saying he was threatened daily → Poland foils alleged assassination plot targeting Prime Minister Donald Tusk

      The membership connection links Duda’s Story to the Tusk follow-up as a consequence; it does not independently prove a causal relationship.

      The membership connection links Duda’s Story to the Tusk follow-up as a consequence; it does not independently prove a causal relationship.

      Footnotes[10][2][1]

    Current related Situations

    Explore all →

    Finding connected developments…

    Compared with currently maintained Situation membership; this list is not part of the retained edition above.

    How a Situation is put together4 Stories · 2 Events · 4 membership connections · 47 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 31 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.