Triple
T28423563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Yaroslavich Khorobrit |
E720009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Vladimir-Suzdal |
C13356
|
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: prince of Vladimir-Suzdal Context triple: [Mikhail Yaroslavich Khorobrit, instanceOf, prince of Vladimir-Suzdal]
-
A.
Grand Prince of Vladimir
chosen
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.
-
B.
Grand Prince of Moscow
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.
Grand Prince of Kiev
The Grand Prince of Kiev was the supreme ruler of Kievan Rus', serving as the principal political, military, and often spiritual leader who held primacy over other regional princes in the federation of East Slavic territories.
-
D.
ruler of Tver
The ruler of Tver is the sovereign authority governing the Principality of Tver, responsible for its political leadership, military command, and administration of justice within its territories.
-
E.
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.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:35 a.m.