Triple
T36046887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Airlines Flight 553 |
E1042695
|
entity |
| Predicate | onboardFatalities |
P33471
|
FINISHED |
| Object | 43 |
—
|
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: 43 | Statement: [United Airlines Flight 553, onboardFatalities, 43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardFatalities Context triple: [United Airlines Flight 553, onboardFatalities, 43]
-
A.
fatalitiesOnboard
chosen
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
B.
aircraftInvolvedInDeath
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
C.
aircraftAccident
Indicates that an event involves an aircraft experiencing an accident, such as a crash, collision, or serious malfunction during operation.
-
D.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
E.
astronautFatalities
Indicates that the situation or event involves the death of one or more astronauts.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.