Triple
T14307974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Horde |
E354746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval khanate |
C12348
|
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: medieval khanate Context triple: [Blue Horde, instanceOf, medieval khanate]
-
A.
medieval Iranian state
A medieval Iranian state is a historically situated political entity in the Iranian plateau and surrounding regions, characterized by dynastic rule, Persianate administrative and cultural traditions, and interaction with neighboring Islamic and Eurasian powers between roughly the 7th and 15th centuries.
-
B.
Turco-Mongol
chosen
Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
-
C.
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.
-
D.
medieval Muslim principality
A medieval Muslim principality is a small, semi-independent political territory ruled by a Muslim prince or governor, typically owing nominal allegiance to a larger empire or caliphate while exercising local authority over military, legal, and economic affairs.
-
E.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.