Triple

T25921697
Position Surface form Disambiguated ID Type / Status
Subject Adana Şakirpaşa Airport E653188 entity
Predicate hasRunway P105 FINISHED
Object Runway 09/27
Runway 09/27 is a primary paved runway at Adana Şakirpaşa Airport in Turkey, aligned roughly east–west to accommodate prevailing winds and commercial air traffic.
E1724096 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 09/27 | Statement: [Adana Şakirpaşa Airport, hasRunway, Runway 09/27]
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 09/27
Triple: [Adana Şakirpaşa Airport, hasRunway, Runway 09/27]
Generated description
Runway 09/27 is a primary paved runway at Adana Şakirpaşa Airport in Turkey, aligned roughly east–west to accommodate prevailing winds and 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_69e7ab3e025c819086771607157f0015 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f603e97750819094072a118a60e332 completed May 2, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11ae921a9c819083fc2f875807478d completed May 23, 2026, 1:41 p.m.
NEDg Description generation batch_6a11afb54ae8819080879d203d92a5c9 completed May 23, 2026, 1:46 p.m.
NED2 Entity disambiguation (via description) batch_6a11b051d328819090f947755dda4cfc completed May 23, 2026, 1:49 p.m.
Created at: April 22, 2026, 8:32 a.m.