Triple
T20120216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutmichevitsa |
E490585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | province of the First Bulgarian Empire |
C42994
|
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: province of the First Bulgarian Empire Context triple: [Kutmichevitsa, instanceOf, province of the First Bulgarian Empire]
-
A.
Bulgarian principality
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.
-
B.
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.
-
C.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
-
D.
region of Bulgaria
A region of Bulgaria is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and natural features.
-
E.
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.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:30 p.m.