Triple
T34763777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Konstantinovich of Suzdal |
E1002141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of 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: ruler of Suzdal Context triple: [Boris Konstantinovich of Suzdal, instanceOf, ruler of Suzdal]
-
A.
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.
-
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 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.
-
D.
ruler of Polotsk
A ruler of Polotsk is the sovereign authority—prince, duke, or monarch—who governed the medieval East Slavic principality of Polotsk, overseeing its political, military, economic, and religious affairs.
-
E.
Prince of Ryazan
The "Prince of Ryazan" is a conceptual class representing a medieval Russian ruler who governs the principality of Ryazan, embodying political authority, military leadership, and dynastic lineage within the historical context of Kievan and post-Kievan Rus.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.