Triple
T35643687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Julius Caesar (Augustus) |
E1029947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founder of the Roman Empire |
C63709
|
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: founder of the Roman Empire Context triple: [Gaius Julius Caesar (Augustus), instanceOf, founder of the Roman Empire]
-
A.
regent of the Western Roman Empire
A regent of the Western Roman Empire was an individual who governed the empire on behalf of an underage, absent, or otherwise incapacitated Western Roman emperor, exercising imperial authority without holding the imperial title.
-
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.
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.
-
D.
3rd-century Roman emperor
A 3rd-century Roman emperor is the sovereign ruler of the Roman Empire during the 200s CE, navigating intense military, political, and economic crises while asserting imperial authority over a vast and often unstable realm.
-
E.
4th-century Roman emperor
A 4th-century Roman emperor is a sovereign ruler of the Roman Empire during the 300s CE, navigating military, religious, and administrative transformations that reshaped the ancient Mediterranean world.
- F. None of above. chosen
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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.