Triple
T16936278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antalya Airport |
E410833
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object | Runway 18R/36L |
E526285
|
NE 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: Runway 18R/36L | Statement: [Antalya Airport, hasRunway, Runway 18R/36L]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 18R/36L Context triple: [Antalya Airport, hasRunway, Runway 18R/36L]
-
A.
Runway 18R/36L
Runway 18R/36L is a primary north–south runway used for commercial air traffic at Cincinnati/Northern Kentucky International Airport.
-
B.
Runway 18R/36L
chosen
Runway 18R/36L is a primary paved runway used for commercial air traffic operations at Antalya Airport in Turkey.
-
C.
Runway 18R/36L
Runway 18R/36L is a primary paved runway used for aircraft takeoffs and landings at Gimhae International Airport in Busan, South Korea.
-
D.
Runway 18R/36L
Runway 18R/36L is a primary north–south runway at Memphis International Airport, used extensively for both commercial and cargo operations.
-
E.
Runway 18R/36L
Runway 18R/36L is a primary paved runway at Napa County Airport in California, used for general aviation and regional air traffic operations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2a05f48190a0a8ac86985f4000 |
completed | April 18, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc04f60081909b7b276a4010c321 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:30 a.m.