Triple
T9819472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetricus II |
E238491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman child ruler |
C13748
|
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: ancient Roman child ruler Context triple: [Tetricus II, instanceOf, ancient Roman child ruler]
-
A.
imperial prince of Rome
chosen
An imperial prince of Rome is a male member of the ruling emperor’s family, often positioned as a potential heir and endowed with high status, privileges, and political influence within the Roman imperial hierarchy.
-
B.
Roman imperial princess
A Roman imperial princess is a female member of the emperor’s family whose status, marriages, and public image were used to secure dynastic legitimacy and political alliances within the Roman Empire.
-
C.
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.
-
D.
King of Rome
The King of Rome is a conceptual class representing the sovereign ruler of the ancient Roman Kingdom, embodying supreme political, religious, and military authority prior to the establishment of the Roman Republic.
-
E.
usurper Roman emperor
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.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:31 p.m.