Triple

T11014958
Position Surface form Disambiguated ID Type / Status
Subject Janid dynasty E260339 entity
Predicate hasCapital P204 FINISHED
Object Samarqand E66141 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: Samarqand | Statement: [Janid dynasty, hasCapital, Samarqand]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Samarqand
Context triple: [Janid dynasty, hasCapital, Samarqand]
  • A. Samarkand chosen
    Samarkand is an ancient Silk Road city in present-day Uzbekistan renowned for its Timurid-era Islamic architecture and role as a major cultural and commercial center of Central Asia.
  • B. 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.
  • C. Taşkent
    Taşkent is a small mountainous district and town in Turkey’s Konya Province, known for its rural character and scenic Anatolian landscape.
  • D. 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.
  • E. Urgench
    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 (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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797a49f648190a5144625d09dec6f completed April 9, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5d2f0f7948190b921c9308489f676 completed April 20, 2026, 7:17 a.m.
Created at: April 8, 2026, 9:25 p.m.