Triple
T36269877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEQU |
E892639
|
entity |
| Predicate | successorAirportIATA |
P45327
|
FINISHED |
| Object | UIO |
—
|
NE NERFINISHED |
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: UIO | Statement: [SEQU, successorAirportIATA, UIO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAirportIATA Context triple: [SEQU, successorAirportIATA, UIO]
-
A.
successorCodeForSameAirport
chosen
Indicates that one code is the direct replacement or follow-up code for the same airport, reflecting a change while the underlying airport remains the same.
-
B.
operatorSecondaryHubAirportIATA
Indicates the IATA airport code of a secondary hub airport used by the operator.
-
C.
destinationAirportICAO
Indicates the airport, identified by its ICAO code, that serves as the destination in a flight or travel-related context.
-
D.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
E.
destinationAirportAlternativeName
Indicates that an airport serves as an alternative or secondary destination for another airport, typically used when the primary destination is unavailable or unsuitable.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:09 p.m.