Triple
T25255021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Airlines Flight 8622 |
E633143
|
entity |
| Predicate | airportClosure |
P16654
|
FINISHED |
| Object | temporary closure of Trabzon Airport |
—
|
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: temporary closure of Trabzon Airport | Statement: [Pegasus Airlines Flight 8622, airportClosure, temporary closure of Trabzon Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportClosure Context triple: [Pegasus Airlines Flight 8622, airportClosure, temporary closure of Trabzon Airport]
-
A.
closedForFlightOperations
chosen
Indicates that a location, facility, or area is temporarily unavailable or prohibited for conducting flight operations.
-
B.
airportOpened
Indicates that an airport began operations or was officially opened at a specific time.
-
C.
airportStatus
Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
-
D.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
E.
sectorClosures
Indicates that specific sectors or areas are closed, restricted, or otherwise unavailable for use or access.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808f350881908ebf53f883f5e5b0 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:13 p.m.