Triple
T28692768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decimus Junius Brutus Albinus |
E729330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman republican politician |
C25185
|
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: [Decimus Junius Brutus Albinus, instanceOf, Roman republican politician]
-
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 Republican-era figure
chosen
A Roman Republican-era figure is an individual who lived and was active during the Roman Republic (c. 509–27 BCE), typically participating in its political, military, social, or cultural life.
-
C.
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.
-
D.
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.
-
E.
legendary Roman figure
A legendary Roman figure is a semi-mythical person from Rome’s past whose life and deeds blend historical elements with folklore to embody key Roman values and origins.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:37 a.m.