Triple
T25023336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Perugia |
E626638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine territorial division |
C47992
|
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 territorial division Context triple: [Duchy of Perugia, instanceOf, Byzantine territorial division]
-
A.
Byzantine theme
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 duchy
chosen
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.
-
E.
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.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.