Triple
T30448986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTA Flight 772 bombing |
E774656
|
entity |
| Predicate | explosiveDeviceLocation |
P18705
|
FINISHED |
| Object | cargo hold |
—
|
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: cargo hold | Statement: [UTA Flight 772 bombing, explosiveDeviceLocation, cargo hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosiveDeviceLocation Context triple: [UTA Flight 772 bombing, explosiveDeviceLocation, cargo hold]
-
A.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
B.
bombingLocation
chosen
Indicates the place where a bombing event occurs or is carried out.
-
C.
detonationPosition
Indicates the specific location or coordinates at which a detonation occurs or is intended to occur.
-
D.
detonatedOutside
Indicates that an explosive device was set off in a location that is outside a specified area or structure.
-
E.
allegedShooterLocation
Indicates the place where a person is claimed or reported to have carried out a shooting.
- 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_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:09 p.m.