Triple
T14003518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokhtamysh |
E336889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Golden Horde ruler |
C7346
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Golden Horde ruler Context triple: [Tokhtamysh, instanceOf, Golden Horde ruler]
-
A.
Mongol ruler
chosen
A Mongol ruler is a sovereign leader of the Mongol people and their empire, wielding military, political, and often spiritual authority over vast, multiethnic territories.
-
B.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
C.
Khan of Bukhara
The Khan of Bukhara is the sovereign ruler of the Khanate of Bukhara, a Central Asian polity historically centered in the city of Bukhara and exercising political, military, and religious authority over its territories.
-
D.
Crimean khan
A Crimean khan was the sovereign ruler of the Crimean Khanate, a Turkic-Mongol state that existed from the 15th to the 18th century under the suzerainty of the Ottoman Empire.
-
E.
Khan of Khiva
The Khan of Khiva was the hereditary ruler of the Khanate of Khiva, a Central Asian polity centered in Khwarezm, who held political, military, and often religious authority over the region until its abolition in the early 20th century.
- F. None of above.
Provenance (1 batch)
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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.