Triple
T14006101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sredny Stog culture |
E336951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pontic–Caspian steppe culture |
C33396
|
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: Pontic–Caspian steppe culture Context triple: [Sredny Stog culture, instanceOf, Pontic–Caspian steppe culture]
-
A.
Eurasian steppe
The Eurasian steppe is a vast belt of temperate grassland stretching from Eastern Europe across Central Asia to Manchuria, characterized by open plains, continental climate, and a long history of nomadic pastoralism and cultural exchange.
-
B.
Eurasian steppe people
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.
-
C.
Sarmatian people
The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
-
D.
Turco-Mongol
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.
-
E.
Slavic culture
Slavic culture encompasses the shared languages, traditions, folklore, religious practices, and social customs of the diverse Slavic peoples of Eastern, Central, and Southeastern Europe.
- F. None of above. chosen
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.