Triple
T30788606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohammad Salameh |
E784024
|
entity |
| Predicate | terroristAttackType |
P4333
|
FINISHED |
| Object | truck bombing |
—
|
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: truck bombing | Statement: [Mohammad Salameh, terroristAttackType, truck bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terroristAttackType Context triple: [Mohammad Salameh, terroristAttackType, truck bombing]
-
A.
typeOfTerrorism
Indicates a classification relationship where an act or event is identified as belonging to a specific category or type of terrorism.
-
B.
usedTerrorism
Indicates that an entity employed or supported acts of terrorism as a means to achieve its objectives.
-
C.
terroristAttackTargetCountry
Indicates that a terrorist attack is directed against or occurs within the specified country as its target.
-
D.
bombingPerpetrator
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
-
E.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6900b856881908453d028f34c1e8f |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:41 p.m.