Triple
T20540796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Vladimirovich of Volhynia |
E504325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Volhynia |
C31698
|
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: prince of Volhynia Context triple: [Roman Vladimirovich of Volhynia, instanceOf, prince of Volhynia]
-
A.
Prince of Volhynia
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Grand Prince of Kiev
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.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:37 a.m.