Triple

T5065030
Position Surface form Disambiguated ID Type / Status
Subject Karshi E114121 entity
Predicate alternativeName P39 FINISHED
Object Karshi, Uzbekistan E489795 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: Karshi, Uzbekistan | Statement: [Karshi, alternativeName, Karshi, Uzbekistan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karshi, Uzbekistan
Context triple: [Karshi, alternativeName, Karshi, Uzbekistan]
  • A. Karshi
    Karshi is a city in southern Uzbekistan known as an important regional center for industry, agriculture, and transportation.
  • B. Bukhara, Uzbekistan
    Bukhara, Uzbekistan is an ancient Silk Road city renowned for its well-preserved Islamic architecture and historic center, a UNESCO World Heritage Site.
  • C. Andijan
    Andijan is a historic city in eastern Uzbekistan, known as a major cultural and economic center of the Fergana Valley and as the birthplace of the Mughal emperor Babur.
  • D. Karaganda
    Karaganda is a large industrial city in central Kazakhstan known for its coal mining industry and Soviet-era history.
  • E. Qarshi chosen
    Qarshi is a historic city in southern Uzbekistan known as a regional economic and cultural center.
  • 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_69bd443c0c8c81908663b77afb28e165 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7478f7988190bc0473e8af055147 completed March 20, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69beb10778208190a5c6a9457c085491 completed March 21, 2026, 2:53 p.m.
Created at: March 20, 2026, 1:38 p.m.