Triple
T20933795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulo |
E515532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgar dynasty |
C31433
|
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: Bulgar dynasty Context triple: [Dulo, instanceOf, Bulgar dynasty]
-
A.
medieval Bulgarian dynasty
chosen
A medieval Bulgarian dynasty is a ruling family that governed the Bulgarian state during the Middle Ages, shaping its political structure, territorial expansion, cultural development, and relations with neighboring powers.
-
B.
Bulgarian royal dynasty
A Bulgarian royal dynasty is a hereditary ruling family that held the throne of Bulgaria over successive generations, shaping the country's political, cultural, and historical development.
-
C.
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.
-
D.
Serbian dynasty
A Serbian dynasty is a hereditary ruling family that governed medieval Serbian states, shaping their political, cultural, and territorial development over successive generations.
-
E.
Bulgarian nobles
Bulgarian nobles are members of the historical aristocratic class in Bulgaria who held hereditary titles, land, and political influence, shaping the country’s medieval and early modern governance, culture, and military affairs.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:49 p.m.