Triple
T33368163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lod Airport massacre |
E854413
|
entity |
| Predicate | oneAttackerSuicideByGrenade |
P163800
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Lod Airport massacre, oneAttackerSuicideByGrenade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneAttackerSuicideByGrenade Context triple: [Lod Airport massacre, oneAttackerSuicideByGrenade, true]
-
A.
oneAttackerKilled
Indicates that exactly one of the attackers involved in the event was killed.
-
B.
weaponUsedOnSelf
chosen
Indicates that an entity uses a weapon against itself, causing self-directed harm or attack.
-
C.
perpetratorDeath
Indicates that the referenced individual is the one who caused or is responsible for another entity’s death.
-
D.
killedByWeaponOf
Indicates that one entity was killed using a weapon that belongs to or is associated with another entity.
-
E.
killedOnGround
Indicates that one entity caused the death of another entity while the victim was on the ground.
- F. None of above.
Provenance (3 batches)
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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.