Triple
T8977332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Kalita |
E214424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Russian ruler |
C7138
|
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: medieval Russian ruler Context triple: [Ivan Kalita, instanceOf, medieval Russian ruler]
-
A.
monarch of Kievan Rus'
A monarch of Kievan Rus' is the supreme hereditary ruler—typically titled grand prince—who governed the medieval East Slavic polity centered on Kyiv, overseeing its military, legal, religious, and diplomatic affairs.
-
B.
Grand Prince of Moscow
chosen
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
-
C.
ruler of Kievan Rus'
A ruler of Kievan Rus' is the supreme political and military leader of the medieval East Slavic state centered in Kyiv, responsible for governing its territories, directing foreign policy, and upholding dynastic authority.
-
D.
Grand Prince of Vladimir
The Grand Prince of Vladimir was the supreme ruler of the medieval principality of Vladimir-Suzdal, holding preeminent authority among the Rus’ princes and serving as a key predecessor to the centralized Russian monarchy.
-
E.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:02 p.m.