Triple
T20092576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Данило Романович |
E496309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | правитель Галицько-Волинської держави |
C12607
|
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.
monarch of Galicia–Volhynia
chosen
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.
-
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.
Polish duke
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
-
D.
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.
-
E.
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.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:22 p.m.