Triple
T24177836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Cypriot airlines |
E599332
|
entity |
| Predicate | typicalHubAirport |
P8171
|
FINISHED |
| Object | Ercan International Airport |
—
|
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: Ercan International Airport | Statement: [Turkish Cypriot airlines, typicalHubAirport, Ercan International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHubAirport Context triple: [Turkish Cypriot airlines, typicalHubAirport, Ercan International Airport]
-
A.
associatedHubAirport
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
-
B.
hubAirport
chosen
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
C.
airlineHub
Indicates that a particular location (typically an airport or city) serves as a central hub or primary operational base for an airline.
-
D.
operatorMainHubAirportCountry
Indicates that an operator’s primary hub airport is located in the specified country.
-
E.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.