Triple

T18370147
Position Surface form Disambiguated ID Type / Status
Subject Erzurum E446160 entity
Predicate transport P230 FINISHED
Object Erzurum Airport NE NERFINISHED

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: Erzurum Airport | Statement: [Erzurum, transport, Erzurum Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erzurum Airport
Context triple: [Erzurum, transport, Erzurum Airport]
  • A. Erzurum Airport chosen
    Erzurum Airport is a public airport serving the city of Erzurum in eastern Turkey, handling both domestic and limited international flights.
  • B. Elazığ Airport
    Elazığ Airport is a public airport in eastern Turkey that serves the city of Elazığ and its surrounding region with domestic flights.
  • C. Sivas Nuri Demirağ Airport
    Sivas Nuri Demirağ Airport is a public airport serving the city and province of Sivas in central Turkey, providing domestic and limited international air connections.
  • D. Muş Airport
    Muş Airport is a regional public airport in eastern Turkey that serves the city of Muş and its surrounding area with domestic flights.
  • E. Erzincan Airport
    Erzincan Airport is a public airport in eastern Turkey that serves the city of Erzincan and its surrounding province with domestic flights.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e51751e4288190873bcc4dc140ac16 completed April 19, 2026, 5:56 p.m.
Created at: April 10, 2026, 10:44 a.m.