Triple
T29519528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol-Tatar troops |
E748892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | steppe nomad warriors |
C27464
|
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: steppe nomad warriors Context triple: [Mongol-Tatar troops, instanceOf, steppe nomad warriors]
-
A.
Turkic warrior
A Turkic warrior is a mounted or foot soldier from the historical Turkic peoples, renowned for their skill in steppe warfare, archery, and cavalry tactics across Eurasia.
-
B.
Indigenous warriors
Indigenous warriors are defenders of their communities and homelands who draw on traditional knowledge, spiritual beliefs, and cultural practices to engage in warfare, resistance, and protection across generations.
-
C.
Eurasian steppe people
chosen
Eurasian steppe people are the historically nomadic and semi-nomadic populations inhabiting the vast grassland belt from Eastern Europe to Mongolia, whose cultures, economies, and warfare were shaped by horse pastoralism and long-distance mobility.
-
D.
nomadic empire
A nomadic empire is a large, often militaristic polity built and ruled by mobile pastoral or steppe peoples who control vast territories and diverse sedentary populations without fully settling them.
-
E.
khans of the White Horde
Khans of the White Horde were the ruling nomadic Turkic-Mongol sovereigns of the eastern Jochid ulus, governing steppe territories in Central Asia and Siberia as part of the wider Mongol Empire’s successor states.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:40 p.m.