Triple
T12660434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman the Great |
E302408
|
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 the Great, instanceOf, Prince of Volhynia]
-
A.
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.
-
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.
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.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
-
E.
Duke of Sieradz
The Duke of Sieradz was a medieval Polish noble title denoting the ruler of the Sieradz region, often held by members of the Piast dynasty during the period of Poland’s territorial fragmentation.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:19 p.m.