Triple
T30151669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usurpation of Procopius |
E766412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial usurpation |
C11362
|
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: Roman imperial usurpation Context triple: [Usurpation of Procopius, instanceOf, Roman imperial usurpation]
-
A.
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.
-
B.
Byzantine civil war
A Byzantine civil war is an internal armed conflict within the Byzantine Empire, typically involving rival claimants to the imperial throne, shifting aristocratic factions, and foreign intervention that weakened central authority.
-
C.
usurper Roman emperor
chosen
A usurper Roman emperor is an individual who illegitimately seizes imperial power, typically through rebellion or military support, without lawful succession or recognition by established authorities.
-
D.
Roman imperial dynasty
A Roman imperial dynasty is a succession of emperors from the same family or household who ruled the Roman Empire over a continuous period, sharing political power, legitimacy, and often common policies or agendas.
-
E.
Third Servile War
The Third Servile War was a major slave uprising against the Roman Republic (73–71 BCE), led by the gladiator Spartacus, which challenged Roman authority in Italy before being brutally suppressed.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:20 p.m.