Triple
T35434472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidin Tsardom |
E1024162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian state |
C31432
|
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 state Context triple: [Vidin Tsardom, instanceOf, medieval Bulgarian state]
-
A.
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.
-
B.
medieval Bulgarian dynasty
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.
-
C.
Bulgarian principality
chosen
A Bulgarian principality is a semi-autonomous, monarchical political entity historically established on Bulgarian territory, typically under the suzerainty or influence of a larger empire or state.
-
D.
province of the First Bulgarian Empire
A province of the First Bulgarian Empire was an administrative-territorial unit governed by imperial officials, responsible for local governance, tax collection, military organization, and the implementation of central authority within a defined region of the empire.
-
E.
Slavic state
A Slavic state is a political entity whose dominant population, culture, and often official language are rooted in one or more Slavic ethnic groups.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.