Triple
T9462978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odaenathus |
E228196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman client king |
C12572
|
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 client king Context triple: [Odaenathus, instanceOf, Roman client king]
-
A.
Roman client ruler
chosen
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.
-
B.
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.
-
C.
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.
-
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.
imperial prince of Rome
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.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:53 p.m.