Triple

T27097329
Position Surface form Disambiguated ID Type / Status
Subject Istanbul Atatürk Airport E686340 entity
Predicate formerName P65 FINISHED
Object Yeşilköy Airport
Yeşilköy Airport was the original name of Istanbul Atatürk Airport, once the main international gateway to Istanbul and one of Turkey’s busiest airports.
E1767243 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: Yeşilköy Airport | Statement: [Istanbul Atatürk Airport, formerName, Yeşilköy Airport]
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: Yeşilköy Airport
Triple: [Istanbul Atatürk Airport, formerName, Yeşilköy Airport]
Generated description
Yeşilköy Airport was the original name of Istanbul Atatürk Airport, once the main international gateway to Istanbul and one of Turkey’s busiest airports.

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_6a129c8c81948190b1a8fbfc88af0ba8 completed May 24, 2026, 6:37 a.m.
NEDg Description generation batch_6a129dc563e081909b6e07e29aad6ddb completed May 24, 2026, 6:42 a.m.
NED2 Entity disambiguation (via description) batch_6a129e62fd248190b264904e77be6e5e completed May 24, 2026, 6:44 a.m.
Created at: April 27, 2026, 8:45 a.m.