Triple
T32209817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegidius |
E822767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of a breakaway Roman domain |
C25704
|
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: ruler of a breakaway Roman domain Context triple: [Aegidius, instanceOf, ruler of a breakaway Roman domain]
-
A.
Gallic Empire ruler
chosen
A Gallic Empire ruler is a sovereign who governed the breakaway Roman state in Gaul, Britain, and sometimes Hispania during the mid-3rd century crisis, asserting imperial authority separate from the central Roman emperors.
-
B.
Roman client ruler
A Roman client ruler was a local king or chieftain who retained nominal authority over their territory while governing under the supervision and in the interests of the Roman Empire.
-
C.
de facto ruler of Rome
The de facto ruler of Rome is the individual or group that, regardless of official titles or legal status, effectively holds and exercises the city’s supreme political and military power.
-
D.
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.
-
E.
legendary Roman king
A legendary Roman king is a semi-mythical early ruler of Rome, often credited in tradition with foundational laws, institutions, or religious practices that shaped Roman identity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:37 a.m.