Triple
T22247220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omurtag of Bulgaria |
E549876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian monarch |
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: medieval Bulgarian monarch Context triple: [Omurtag of Bulgaria, instanceOf, medieval Bulgarian monarch]
-
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.
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.
-
C.
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.
-
D.
medieval Serbian king
A medieval Serbian king is a sovereign ruler of the Serbian medieval state, embodying both political authority and often sacral legitimacy while governing feudal territories, leading military campaigns, and patronizing the Orthodox Church and culture.
-
E.
Tsaritsa of Bulgaria
The Tsaritsa of Bulgaria is the title given to the queen consort or reigning queen of Bulgaria, traditionally the wife of the Bulgarian tsar, who holds a prominent ceremonial and dynastic role in the Bulgarian monarchy.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:38 p.m.