Triple
T27304607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail of Tver |
E689016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Tver |
C52714
|
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 Tver Context triple: [Mikhail of Tver, instanceOf, ruler of Tver]
-
A.
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.
-
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.
ruler of Moldavia
A ruler of Moldavia is the sovereign leader who historically governed the principality of Moldavia, overseeing its political, military, and administrative affairs.
-
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.
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. chosen
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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:24 a.m.