Triple
T15551273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchy of Nizhny Novgorod-Suzdal |
E370749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vassal state of the Golden Horde |
C3295
|
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: vassal state of the Golden Horde Context triple: [Grand Duchy of Nizhny Novgorod-Suzdal, instanceOf, vassal state of the Golden Horde]
-
A.
Mongol successor state
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
-
B.
vassal state
chosen
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
C.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
D.
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.
-
E.
medieval East Slavic state
A medieval East Slavic state is a historically situated political entity formed by East Slavic peoples between the 9th and 15th centuries, characterized by princely rule, Orthodox Christianity, and a feudal socio-economic structure.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:08 a.m.