Triple
T15583061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macedonia (Byzantine theme) |
E374547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine administrative division |
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: Byzantine administrative division Context triple: [Macedonia (Byzantine theme), instanceOf, Byzantine administrative division]
-
A.
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.
-
B.
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.
-
C.
Eastern Roman Empire
The Eastern Roman Empire, also known as the Byzantine Empire, was the continuation of the Roman Empire in its eastern provinces, centered on Constantinople, that preserved Roman governance, law, and culture while developing a distinct Greek-speaking Christian civilization from late antiquity through the Middle Ages.
-
D.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
E.
Byzantine law code
A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:11 a.m.