Triple
T9953076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubart |
E195376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Ruthenian prince |
C12606
|
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: medieval Ruthenian prince Context triple: [Lubart, instanceOf, medieval Ruthenian prince]
-
A.
Rurikid prince
chosen
A Rurikid prince is a medieval ruler or dynastic member descended from the Varangian leader Rurik, who governed principalities across Kievan Rus' and its successor states.
-
B.
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.
-
C.
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.
-
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.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.