Triple
T5942961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon I of Bulgaria |
E132211
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tsar of Bulgaria |
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: tsar of Bulgaria Context triple: [Simeon I of Bulgaria, instanceOf, tsar of Bulgaria]
-
A.
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.
-
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 Russia
The tsar of Russia was the autocratic monarch who ruled the Russian state and later empire, wielding supreme political, military, and religious authority until the monarchy’s abolition in 1917.
-
D.
King of Yugoslavia
The King of Yugoslavia was the hereditary monarch and head of state of the Kingdom of Yugoslavia, symbolizing national unity and holding supreme authority within its constitutional framework.
-
E.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:01 p.m.