Triple
T9087367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Licinius Lucullus |
E217792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Republican politician |
C6905
|
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 Republican politician Context triple: [Lucius Licinius Lucullus, instanceOf, Roman Republican politician]
-
A.
Roman senator
chosen
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 reformer
A Roman reformer is an individual in ancient Rome who sought to change political, social, or economic structures through legislation, public advocacy, or institutional innovation to address perceived injustices or inefficiencies.
-
D.
Roman philosopher
A Roman philosopher is a thinker from ancient Rome who engaged in the systematic study of ethics, logic, politics, and the nature of reality, often blending Greek philosophical traditions with Roman cultural and practical concerns.
-
E.
Roman historian
A Roman historian is a scholar or writer from ancient Rome who researched, recorded, and interpreted past events of Rome and its world, often blending factual reporting with rhetorical and moral commentary.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:13 p.m.