Triple

T17948345
Position Surface form Disambiguated ID Type / Status
Subject Khwarazmian Shah E448762 entity
Predicate capital P234 FINISHED
Object Gurganj 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: Gurganj | Statement: [Khwarazmian Shah, capital, Gurganj]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurganj
Context triple: [Khwarazmian Shah, capital, Gurganj]
  • A. 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.
  • B. Afrasiab
    Afrasiab is a legendary Turanian king and formidable adversary of Iran in the Persian epic Shahnameh.
  • C. Panjikent
    Panjikent was an important ancient Sogdian city in present-day Tajikistan, known for its well-preserved wall paintings and role as a Silk Road trading center.
  • D. Tushpa
    Tushpa was the ancient fortified city on the eastern shore of Lake Van that served as the political and cultural center of the Kingdom of Urartu in the early first millennium BCE.
  • E. Urgench chosen
    Urgench is a city in western Uzbekistan that serves as the administrative center of Khorezm Region and a gateway to the historic city of Khiva.
  • 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afa9cb2481908c95f8c430dcc0aa completed April 19, 2026, 10:34 a.m.
Created at: April 10, 2026, 10:21 a.m.