Triple
T33368164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lod Airport massacre |
E854413
|
entity |
| Predicate | oneAttackerCaptured |
P172714
|
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, oneAttackerCaptured, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneAttackerCaptured Context triple: [Lod Airport massacre, oneAttackerCaptured, true]
-
A.
capturedAttacker
chosen
Indicates that an entity has successfully apprehended or taken control of an attacking entity.
-
B.
oneAttackerKilled
Indicates that exactly one of the attackers involved in the event was killed.
-
C.
belligerentSideAfterCapture
Indicates the party or side that an entity belongs to after it has been captured in a conflict or competitive interaction.
-
D.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
E.
capturedOff
Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:35 a.m.