Triple
T30681271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saloninus |
E781057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial claimant |
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 claimant Context triple: [Saloninus, instanceOf, Roman imperial claimant]
-
A.
Byzantine imperial pretender
A Byzantine imperial pretender is an individual who, without universally recognized legitimacy, claims the title and authority of Byzantine emperor in opposition to the reigning or established ruler.
-
B.
legendary Roman prince
A legendary Roman prince is a semi-mythical noble figure from ancient Rome, often depicted as embodying idealized virtues such as bravery, honor, and leadership, and frequently associated with foundational or heroic tales of the Roman state.
-
C.
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.
-
D.
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.
-
E.
Gallic Empire ruler
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.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.