Triple
T25182518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Airlines Flight 2193 |
E630621
|
entity |
| Predicate | runwayOverrun |
P160104
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pegasus Airlines Flight 2193, runwayOverrun, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayOverrun Context triple: [Pegasus Airlines Flight 2193, runwayOverrun, true]
-
A.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
B.
runwayCrosses
Indicates that one runway intersects or passes across another runway or designated path.
-
C.
runwayApproachOver
Indicates that an aircraft’s approach path to a runway passes over a particular object, area, or feature.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
runwayPerformance
Indicates the performance characteristics or behavior of an entity (such as an aircraft or vehicle) when operating on a runway, including factors like acceleration, deceleration, and required distances.
- 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_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 21, 2026, 12:36 p.m.