Triple
T2110075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Airlines Flight 175 |
E42480
|
entity |
| Predicate | fatalitiesOnBoard |
P33471
|
FINISHED |
| Object | 65 |
—
|
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: 65 | Statement: [United Airlines Flight 175, fatalitiesOnBoard, 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatalitiesOnBoard Context triple: [United Airlines Flight 175, fatalitiesOnBoard, 65]
-
A.
fatalitiesOnboard
chosen
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
B.
crewFatality
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
C.
fatalitiesCategory
Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
diedOnJourneyBetween
Indicates that an entity died while traveling between two specified locations or points in a journey.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae1bacc8190beffc9d0470e9190 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.