Triple
T2101009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Byzantine period |
E37091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | era of the Byzantine Empire |
C9833
|
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: era of the Byzantine Empire Context triple: [Late Byzantine period, instanceOf, era of the Byzantine Empire]
-
A.
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.
-
B.
Western Roman emperor
A Western Roman emperor is the sovereign ruler of the western half of the Roman Empire, holding supreme political, military, and religious authority from the late 3rd to the late 5th century CE.
-
C.
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.
-
D.
ancient empire
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
E.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.