Triple
T33652745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU-GAP |
E862140
|
entity |
| Predicate | fatalitiesOnAccidentFlight |
P33471
|
FINISHED |
| Object | 217 |
—
|
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: 217 | Statement: [SU-GAP, fatalitiesOnAccidentFlight, 217]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatalitiesOnAccidentFlight Context triple: [SU-GAP, fatalitiesOnAccidentFlight, 217]
-
A.
fatalitiesOnboard
chosen
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
B.
aircraftAccident
Indicates that an event involves an aircraft experiencing an accident, such as a crash, collision, or serious malfunction during operation.
-
C.
flightNumberInAccident
Indicates that a specific flight number is associated with an accident event.
-
D.
aircraftInvolvedInDeath
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
E.
groundCrewFatalitiesInFinalAccident
Indicates the number of ground crew members who were killed in the final accident associated with the event or entity.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.