Triple
T33048929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunnic Empire |
E845672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | steppe polity |
C8658
|
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 polity Context triple: [Hunnic Empire, instanceOf, steppe polity]
-
A.
Slavic polity
A Slavic polity is a political entity—such as a tribe, principality, kingdom, or state—primarily composed of Slavic peoples and shaped by their shared linguistic, cultural, and historical traditions.
-
B.
Pontic–Caspian steppe culture
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.
-
C.
Oghuz Turkic polity
An Oghuz Turkic polity is a socio-political entity formed by Oghuz Turkic groups, typically characterized by tribal confederation structures, nomadic or semi-nomadic lifeways, and rule by military-elite lineages asserting authority over diverse subject populations.
-
D.
Central Asian polity
chosen
A Central Asian polity is a political entity—such as a state, khanate, emirate, or tribal confederation—centered in the Central Asian region, shaped by its steppe geography, Silk Road connections, and interactions among Turkic, Persian, Mongol, and other cultural influences.
-
E.
Central Asian polity
A Central Asian polity is a historically or contemporarily organized political entity—such as a state, khanate, or empire—centered in the Central Asian region, characterized by its governance structures, territorial control, and interactions with neighboring powers.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.