Triple
T24104602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 Kiryat Shmona massacre |
E597186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Palestinian militant attack |
C3655
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Palestinian militant attack Context triple: [1974 Kiryat Shmona massacre, instanceOf, Palestinian militant attack]
-
A.
Palestinian militant
A Palestinian militant is an individual, typically affiliated with an armed political or ideological group, who engages in or supports the use of force in pursuit of Palestinian national or political objectives.
-
B.
terrorist attack
chosen
A terrorist attack is a deliberate act of violence or threat of violence, typically against civilians or symbolic targets, carried out to instill fear and advance political, ideological, or religious objectives.
-
C.
Zionist paramilitary campaign
Zionist paramilitary campaign refers to the organized use of armed force and covert operations by Jewish nationalist groups, primarily in Mandatory Palestine, to advance the establishment and defense of a Jewish state.
-
D.
Palestinian militant group
A Palestinian militant group is an organized, often armed, non-state actor that uses violence or the threat of violence, typically framed as resistance or struggle, to pursue political, ideological, or territorial objectives related to the Palestinian cause.
-
E.
terrorist attack target
A terrorist attack target is any person, place, system, or symbolic asset deliberately selected by terrorists to inflict harm, create fear, or achieve political, ideological, or religious objectives.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:01 p.m.