Triple

T19402002
Position Surface form Disambiguated ID Type / Status
Subject Nukus Airport E485346 entity
Predicate serves P98 FINISHED
Object Nukus 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: Nukus | Statement: [Nukus Airport, serves, Nukus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nukus
Context triple: [Nukus Airport, serves, Nukus]
  • A. Nukus chosen
    Nukus is the capital of the autonomous Republic of Karakalpakstan in western Uzbekistan, known for its remote desert location and the renowned Nukus Museum of Art.
  • B. Yoshkar-Ola
    Yoshkar-Ola is a city in central Russia that serves as the administrative, cultural, and economic center of the Mari El Republic.
  • C. Tashkent
    Tashkent is the capital and largest city of Uzbekistan, a major cultural and economic hub in Central Asia with deep historical ties to the Islamic world.
  • D. Qarshi
    Qarshi is a historic city in southern Uzbekistan known as a regional economic and cultural center.
  • E. Kokshetau
    Kokshetau is a city in northern Kazakhstan that serves as the administrative and economic center of the surrounding Akmola Region.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62577f808819099e74feab82b34a4 completed April 20, 2026, 1:09 p.m.
Created at: April 10, 2026, 1:36 p.m.