Triple
T16846962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Kyril of Bulgaria |
E409566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian prince |
C14364
|
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: Bulgarian prince Context triple: [Prince Kyril of Bulgaria, instanceOf, Bulgarian prince]
-
A.
Prince of Bulgaria
chosen
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.
Bulgarian ruler
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.
-
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.
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.
-
E.
Bulgarian noble
A Bulgarian noble is a member of the historical aristocratic class in Bulgaria, holding hereditary titles, land, and political influence within the medieval or early modern Bulgarian state.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.