Triple
T33652746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU-GAP |
E862140
|
entity |
| Predicate | survivorsOnAccidentFlight |
P162692
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [SU-GAP, survivorsOnAccidentFlight, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsOnAccidentFlight Context triple: [SU-GAP, survivorsOnAccidentFlight, 0]
-
A.
survivorsInFinalAccident
Indicates that the referenced entities are those who remained alive after the final accident in a sequence of accidents.
-
B.
passengerSurvivors
Indicates that the related passengers survived an incident or event.
-
C.
survivedAccident
chosen
Indicates that an entity continued to live or remain unharmed after being involved in an accident.
-
D.
survivorsWhenSunk
Indicates that when an entity (such as a vessel) was sunk, there were survivors from that event.
-
E.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
- 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:42 a.m.