Triple

T9082573
Position Surface form Disambiguated ID Type / Status
Subject Nadym E217669 entity
Predicate hasAirport P105 FINISHED
Object Nadym Airport E233053 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: Nadym Airport | Statement: [Nadym, hasAirport, Nadym Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nadym Airport
Context triple: [Nadym, hasAirport, Nadym Airport]
  • A. Nadym Airport chosen
    Nadym Airport is a regional airport in Nadym, Russia, primarily serving as a key base for operations in the Yamalo-Nenets Autonomous Okrug.
  • B. Anadyr Ugolny Airport
    Anadyr Ugolny Airport is a regional airport in Russia’s far eastern Chukotka Autonomous Okrug that serves the town of Anadyr and connects it to other remote Arctic and Siberian destinations.
  • C. Batagay Airport
    Batagay Airport is a small regional airport in the Sakha Republic of Russia that serves the remote settlement of Batagay and surrounding areas in the Arctic region.
  • D. Sary-Arka Airport
    Sary-Arka Airport is the main international airport serving the city of Karaganda in central Kazakhstan.
  • E. Almaza Airport
    Almaza Airport is a historic airfield in Cairo that served as the city's main airport before the opening of Cairo International Airport.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca83d7a0388190ba1af89ed7ba36f9 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc960a2760819084aab611eb1c43a9 completed April 1, 2026, 3:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69d02ffa9fb88190ab088be46b566ae8 completed April 3, 2026, 9:24 p.m.
Created at: March 30, 2026, 7:13 p.m.