Triple
T610873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Empire |
E12095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor state of the Roman Empire |
C397
|
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: successor state of the Roman Empire Context triple: [Byzantine Empire, instanceOf, successor state of the Roman Empire]
-
A.
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.
-
B.
Islamic empire
An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
-
C.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
D.
former sovereign state
chosen
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
-
E.
colonial empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:35 p.m.