Triple
T22186015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Tarquinius Superbus |
E548298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary king of Rome |
C18863
|
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: legendary king of Rome Context triple: [Lucius Tarquinius Superbus, instanceOf, legendary king of Rome]
-
A.
legendary Roman king
chosen
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.
-
B.
dictator of the Roman Republic
A dictator of the Roman Republic was an extraordinary magistrate appointed during emergencies with supreme, but temporary, authority over civil and military affairs, superseding all other officials.
-
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.
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.
Gallic emperor
A Gallic emperor is a ruler who claimed imperial authority over the breakaway Gallic Empire (comprising parts of Roman Gaul, Britain, and sometimes Spain) during the 3rd-century Crisis of the Roman Empire.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.