Triple
T33149463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дмитрий Александрович |
E848395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | удельный князь |
C58187
|
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: удельный князь Context triple: [Дмитрий Александрович, instanceOf, удельный князь]
-
A.
удельный князь
chosen
Удельный князь — это феодальный правитель, управляющий отдельным уделом (княжеством) в составе более крупного государства, обладающий наследственной властью и относительной политической самостоятельностью.
-
B.
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.
-
C.
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.
-
D.
Prince of Chernigov
The Prince of Chernigov was a medieval ruler of the Chernigov principality in Kievan Rus', holding political, military, and economic authority over the region and its territories.
-
E.
Prince of Galicia
A Prince of Galicia is a royal male heir or ruler associated with the historical region of Galicia, holding dynastic authority, territorial rights, and political influence within its medieval or early modern monarchy.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.