Triple
T1703422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optimates |
E36816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political group |
C9117
|
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 political group Context triple: [Optimates, instanceOf, Roman political group]
-
A.
Roman senator
A Roman senator is a high-ranking political figure in ancient Rome who participates in legislative, advisory, and administrative decision-making within the Senate, influencing the governance and policies of the Roman state.
-
B.
Roman consul
A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
-
C.
Roman censor
A Roman censor was a high-ranking magistrate responsible for conducting the census, overseeing public morals, and managing certain aspects of state finances and public works in the Roman Republic.
-
D.
component of the Roman state
chosen
A component of the Roman state is any institutional, social, or political element—such as magistracies, assemblies, the Senate, legal frameworks, or provincial administrations—that collectively structured and maintained Roman governance and public life.
-
E.
Roman aristocrat
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political influence, owns extensive land and slaves, and upholds traditional social and cultural norms of the elite.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.