Triple
T5827061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris I of Bulgaria |
E129253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian ruler |
C14363
|
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 Bulgarian ruler Context triple: [Boris I of Bulgaria, instanceOf, medieval Bulgarian ruler]
-
A.
Prince of Bulgaria
A Prince of Bulgaria is a male royal titleholder, typically a son or close male relative of the reigning Bulgarian monarch, who holds a defined place in the line of succession and represents the Bulgarian royal family in ceremonial and dynastic roles.
-
B.
Tsar of Bulgaria
chosen
The Tsar of Bulgaria was the monarchic ruler of the Bulgarian state, holding supreme political and often religious authority over the country during its medieval and modern imperial periods.
-
C.
Yugoslav prince
A Yugoslav prince is a male member of the royal family of the former Kingdom of Yugoslavia, typically holding hereditary titles and roles within the monarchy’s dynastic and ceremonial traditions.
-
D.
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.
-
E.
monarch of Kievan Rus'
A monarch of Kievan Rus' is the supreme hereditary ruler—typically titled grand prince—who governed the medieval East Slavic polity centered on Kyiv, overseeing its military, legal, religious, and diplomatic 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.