Triple
T16936277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antalya Airport |
E410833
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object |
Runway 18L/36R
Runway 18L/36R is one of the primary paved runways at Antalya Airport in Turkey, used for handling commercial air traffic.
|
E1242782
|
NE FINISHED |
How this triple was built (4 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 18L/36R | Statement: [Antalya Airport, hasRunway, Runway 18L/36R]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 18L/36R Context triple: [Antalya Airport, hasRunway, Runway 18L/36R]
-
A.
Runway 18L/36R
Runway 18L/36R is a primary north–south runway used for commercial air traffic at Orlando International Airport in Orlando, Florida.
-
B.
Runway 18L/36R
Runway 18L/36R is a primary paved runway used for aircraft takeoffs and landings at Shanghai Hongqiao International Airport.
-
C.
Runway 18L/36R
Runway 18L/36R is a primary north–south runway at Memphis International Airport used for both passenger and cargo aircraft operations.
-
D.
Runway 18L/36R
Runway 18L/36R is a primary paved runway at Boryspil International Airport near Kyiv, Ukraine, used for handling commercial air traffic.
-
E.
Runway 18R/36L
Runway 18R/36L is a primary north–south runway used for commercial air traffic at Cincinnati/Northern Kentucky International Airport.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Runway 18L/36R Triple: [Antalya Airport, hasRunway, Runway 18L/36R]
Generated description
Runway 18L/36R is one of the primary paved runways at Antalya Airport in Turkey, used for handling commercial air traffic.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Runway 18L/36R Target entity description: Runway 18L/36R is one of the primary paved runways at Antalya Airport in Turkey, used for handling commercial air traffic.
-
A.
Runway 18L/36R
Runway 18L/36R is a primary north–south runway used for commercial air traffic at Orlando International Airport in Orlando, Florida.
-
B.
Runway 18L/36R
Runway 18L/36R is a primary paved runway used for aircraft takeoffs and landings at Shanghai Hongqiao International Airport.
-
C.
Runway 18L/36R
Runway 18L/36R is a primary north–south runway at Memphis International Airport used for both passenger and cargo aircraft operations.
-
D.
Runway 18L/36R
Runway 18L/36R is a primary paved runway at Boryspil International Airport near Kyiv, Ukraine, used for handling commercial air traffic.
-
E.
Runway 18R/36L
Runway 18R/36L is a primary paved runway used for commercial air traffic operations at Antalya Airport in Turkey.
- F. None of above. chosen
Provenance (5 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_6a00d45e64d881909da963825d2eea98 |
completed | May 10, 2026, 6:54 p.m. |
| NEDg | Description generation | batch_6a00d587299081908981bd8bc2ae8f3d |
completed | May 10, 2026, 6:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a00d6085cc08190bc3c574ce61d19f4 |
completed | May 10, 2026, 7:01 p.m. |
Created at: April 10, 2026, 5:30 a.m.