Triple
T30162060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Licinius Crassus Dives Mucianus |
E766692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman pontifex maximus |
C23674
|
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 pontifex maximus Context triple: [Publius Licinius Crassus Dives Mucianus, instanceOf, ancient Roman pontifex maximus]
-
A.
pontifex maximus
chosen
The pontifex maximus was the chief high priest of the College of Pontiffs in ancient Rome, overseeing state religion, sacred law, and major religious ceremonies.
-
B.
Augustus (title)
Augustus (title) is an honorific adopted by Roman emperors, beginning with Octavian in 27 BCE, signifying supreme authority, revered status, and the sanctified leadership of the Roman state.
-
C.
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.
-
D.
Caesar of the Roman Empire
A "Caesar of the Roman Empire" is a high-ranking imperial title originally denoting the designated heir or junior co-emperor within the Roman imperial succession system.
-
E.
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.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:22 p.m.