Triple

T27097334
Position Surface form Disambiguated ID Type / Status
Subject Istanbul Atatürk Airport E686340 entity
Predicate runway P1654 FINISHED
Object Runway 17R/35L
Runway 17R/35L is one of the primary paved runways at the former Istanbul Atatürk Airport, used for handling a significant share of the airport’s commercial air traffic.
E1882912 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 17R/35L | Statement: [Istanbul Atatürk Airport, runway, Runway 17R/35L]
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 17R/35L
Triple: [Istanbul Atatürk Airport, runway, Runway 17R/35L]
Generated description
Runway 17R/35L is one of the primary paved runways at the former Istanbul Atatürk Airport, used for handling a significant share of the airport’s commercial air traffic.

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_69ef1489f8b481908e24a1985982bd26 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f623b1d8b48190ae71d57f60d2e327 completed May 2, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a26c8c22ea48190a65b03959f8ef078 completed June 8, 2026, 1:50 p.m.
NEDg Description generation batch_6a26ce72be108190863056913dd23edd completed June 8, 2026, 2:15 p.m.
NED2 Entity disambiguation (via description) batch_6a26d384799481908d7e7b2da5d3fe3c completed June 8, 2026, 2:36 p.m.
Created at: April 27, 2026, 8:45 a.m.