Triple
T32359258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orenburg Cossack Host ataman |
E826814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack ataman |
C10669
|
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: Cossack ataman Context triple: [Orenburg Cossack Host ataman, instanceOf, Cossack ataman]
-
A.
Cossack
chosen
A Cossack is a member of a traditionally semi-military, self-governing community from the steppes of Eastern Europe, renowned for their horsemanship, warrior culture, and role in regional defense and expansion.
-
B.
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.
-
C.
Fedaykin commander
A Fedaykin commander is a highly skilled and fanatically loyal leader of elite desert guerrilla fighters, orchestrating covert operations and battlefield tactics with precision and unwavering devotion to their cause.
-
D.
Muscovite boyar
A Muscovite boyar was a high-ranking noble in medieval and early modern Muscovy who held extensive land, political influence, and advisory roles at the tsar’s court.
-
E.
Bulgar khan
A Bulgar khan is the supreme ruler of the early medieval Bulgar people, combining military leadership, political authority, and often sacral or semi-divine status within their nomadic or semi-nomadic state.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:49 a.m.