Triple
T21095784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volodymyr the Great |
E519761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Prince of Kyiv |
C13276
|
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: Grand Prince of Kyiv Context triple: [Volodymyr the Great, instanceOf, Grand Prince of Kyiv]
-
A.
Grand Prince of Kiev
chosen
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.
-
B.
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.
-
C.
Prince of Volhynia
A Prince of Volhynia was a medieval ruler of the Volhynia principality in the historical region of Ruthenia, exercising political, military, and administrative authority over its territories and people.
-
D.
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.
-
E.
monarch of Galicia–Volhynia
The monarch of Galicia–Volhynia was the sovereign ruler of the medieval East Slavic kingdom of Galicia–Volhynia, exercising supreme political, military, and judicial authority over its territories and subjects.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:52 p.m.