Triple
T30448987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTA Flight 772 bombing |
E774656
|
entity |
| Predicate | explosiveDeviceType |
P113076
|
FINISHED |
| Object | suitcase bomb |
—
|
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: suitcase bomb | Statement: [UTA Flight 772 bombing, explosiveDeviceType, suitcase bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosiveDeviceType Context triple: [UTA Flight 772 bombing, explosiveDeviceType, suitcase bomb]
-
A.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
B.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
C.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
D.
bombType
chosen
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
E.
explosiveLensType
Indicates the specific design or configuration of the explosive lens used to shape and direct the detonation wave.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:09 p.m.