Triple
T25182549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Airlines Flight 2193 |
E630621
|
entity |
| Predicate | passengerSurvivors |
P158782
|
FINISHED |
| Object | 174 |
—
|
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: 174 | Statement: [Pegasus Airlines Flight 2193, passengerSurvivors, 174]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerSurvivors Context triple: [Pegasus Airlines Flight 2193, passengerSurvivors, 174]
-
A.
shipSurvived
Indicates that a ship remained intact and continued to exist or operate after a potentially destructive event or period.
-
B.
survivorsWhenSunk
Indicates that when an entity (such as a vessel) was sunk, there were survivors from that event.
-
C.
crewSurvivorsOnReturn
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
-
D.
survivorsLandingPlace
Indicates the location where survivors arrived or were brought after an incident or 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. chosen
Provenance (4 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 12:36 p.m.