Triple
T3374174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintus Fabius Maximus Verrucosus |
E71025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | censor of the Roman Republic |
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: censor of the Roman Republic Context triple: [Quintus Fabius Maximus Verrucosus, instanceOf, censor of the Roman Republic]
-
A.
Roman censor
chosen
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.
-
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.
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.
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.
-
E.
Theatine priest
A Theatine priest is a member of the Clerics Regular of the Theatines, a Catholic religious order of priests devoted to reforming the clergy and promoting piety through strict communal life, pastoral work, and liturgical service.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.