Triple
T22756035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presian I of Bulgaria |
E562845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of the First Bulgarian Empire |
C18905
|
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: ruler of the First Bulgarian Empire Context triple: [Presian I of Bulgaria, instanceOf, ruler of the First Bulgarian Empire]
-
A.
Bulgarian ruler
chosen
A Bulgarian ruler is a sovereign leader or monarch who has held supreme political authority over the territory and people of Bulgaria throughout its historical periods.
-
B.
Tsar of Bulgaria
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.
Slavic ruler
A Slavic ruler is a sovereign leader or monarch from a Slavic people or state, historically responsible for governance, military command, and the administration of justice within their realm.
-
D.
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.
-
E.
ruler of Kievan Rus'
A ruler of Kievan Rus' is the supreme political and military leader of the medieval East Slavic state centered in Kyiv, responsible for governing its territories, directing foreign policy, and upholding dynastic authority.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:25 p.m.