Triple
T12486444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terter dynasty |
E298444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian royal dynasty |
C31534
|
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 royal dynasty Context triple: [Terter dynasty, instanceOf, Bulgarian royal dynasty]
-
A.
House of Karađorđević
The House of Karađorđević is a Serbian royal dynasty that ruled Serbia and later the Kingdom of Serbs, Croats and Slovenes (Yugoslavia), playing a central role in the region’s 19th- and 20th-century political history.
-
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.
medieval Serbian dynasty
A medieval Serbian dynasty is a ruling family that governed Serbian territories during the Middle Ages, shaping the region’s political, cultural, and religious development through hereditary succession and dynastic alliances.
-
D.
Bulgar state
A Bulgar state is a political entity historically founded and ruled by the Bulgar people, typically characterized by a semi-nomadic warrior elite governing settled agricultural populations within a defined territory.
-
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. chosen
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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.