Triple
T32579980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mubarak Giray |
E832754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Crimean Khanate ruling elite |
C47972
|
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: member of the Crimean Khanate ruling elite Context triple: [Mubarak Giray, instanceOf, member of the Crimean Khanate ruling elite]
-
A.
member of the Giray dynasty
chosen
A member of the Giray dynasty is an individual belonging to the hereditary ruling family of the Crimean Khanate, traditionally claiming descent from Genghis Khan and holding political, military, or noble status within its historical power structure.
-
B.
Timurid noble
A Timurid noble is a high-ranking aristocrat within the Timurid Empire, typically of Turco-Mongol lineage, who held land, military command, and administrative authority under the dynasty founded by Timur (Tamerlane).
-
C.
ruler of Kazan Khanate
The ruler of the Kazan Khanate was the sovereign khan who governed the Tatar state of Kazan, overseeing its political, military, economic, and religious affairs from its establishment in the 15th century until its conquest by Russia in 1552.
-
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.
Ottoman vassal ruler
An Ottoman vassal ruler was a semi-autonomous local sovereign who governed a territory under the suzerainty of the Ottoman Empire, owing tribute, military support, and political loyalty while retaining limited internal authority.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.