Connected Situation / Through 2026-10-31

Israeli Election Irregularities Dispute

stories: 5
events: 2
entities: 47
connections: 5

Evidence so far on 2026-10-31 UTC · updated 2026-10-31 11:21 UTC · analysis as of 2026-10-31 05:33 UTCSign in for the live Situation ↗

Narrative

As-of analysis

Carried forward

Situation at a glance

On October 28, Likud demanded a probe into alleged election fraud by Arab parties; the Event is linked to “Likud claims Israel’s elections were stolen,” which reported Likud’s claim on October 29. On October 29, Israeli police rejected Likud’s election-irregularities claims, while “Likud claims Israel’s elections were stolen” reported Likud’s broader allegation. Also dated October 29, Shin Bet denied targeting Arab voters in the election probe. On October 30, the Central Elections Committee said the Shin Bet probe did not affect results or target a sector. That day, “Israeli police set to release three activists arrested over alleged voter bribery” reported a planned release, while “Israeli election: candidates narrowly miss seats in the 26th Knesset” reported candidate outcomes.

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

Assessment

Likud’s demand and stolen-election claim, the police rejection, Shin Bet’s denial, and the committee’s assessment establish competing claims and official responses, but do not establish whether election fraud occurred. The committee’s statement addresses whether the Shin Bet probe affected results or targeted a sector; it is not independent proof of the underlying allegation. The police-release story describes a planned release in a voter-bribery case, and the candidate-outcome story concerns the same election, but neither establishes that the irregularities claims changed election results.

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

Explanation originally captured 2026-10-31 · Evidence through 2026-10-31 UTC · Source edition sed_8b24c3a8b74314fbf19b64366404c506

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 5 member Stories.
Coded activity
The coded activity is led by 016 · Deny Responsibility (1) and 10 · Demand (1).
Prominent subjects
Likud and Shin Bet are prominent in the retained actor and relationship evidence.
Entity coverage
47 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.

Magnitude4

min 3max 5

2 measured

Systemic importance0.11

min 0.11max 0.12

2 measured

Propagation potential0.27

min 0.25max 0.28

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+ (2 political)

Significance · 20.3
min 0.22max 0.38
Magnitude · 24
min 3max 5
Systemic · 20.11
min 0.11max 0.12
Propagation · 20.27
min 0.25max 0.28
Market · 20.05
min 0.05max 0.05
Goldstein · 2-2.5
min -5max 0
Confidence · 20.55
min 0.3max 0.79

Quad class over those 2 events · Verbal Conflict 1 · Verbal Cooperation 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero.