Triple
T28774610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Μυστράς |
E726499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | βυζαντινή καστροπολιτεία |
C20180
|
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: βυζαντινή καστροπολιτεία Context triple: [Μυστράς, instanceOf, βυζαντινή καστροπολιτεία]
-
A.
Byzantine duchy
A Byzantine duchy was an administrative and military district of the Byzantine Empire governed by a duke (doux), responsible for regional defense, taxation, and local governance under imperial authority.
-
B.
Byzantine regency
Byzantine regency refers to the temporary governance arrangement in the Byzantine Empire whereby one or more regents exercised imperial authority on behalf of an underage, absent, or incapacitated emperor.
-
C.
Byzantine client kingdom
A Byzantine client kingdom was a semi-autonomous state that maintained its own local rulers and internal governance while recognizing the suzerainty of the Byzantine Empire, often providing military support, tribute, or political allegiance in exchange for protection and legitimacy.
-
D.
Byzantine theme
chosen
A Byzantine theme was a military-administrative district of the Byzantine Empire, governed by a strategos who oversaw both civil administration and regional defense.
-
E.
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.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:17 a.m.