Triple
T33709920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timber-grave culture |
E863706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eurasian 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: Eurasian steppe culture Context triple: [Timber-grave culture, instanceOf, Eurasian steppe culture]
-
A.
Pontic–Caspian steppe culture
chosen
The Pontic–Caspian steppe culture refers to the prehistoric and early historic societies that inhabited the vast grasslands north of the Black and Caspian Seas, often associated with early Indo-European migrations, pastoral nomadism, and kurgan burial traditions.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.