Triple
T5873987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pliny the Elder |
E130583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military officer |
C10598
|
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 military officer Context triple: [Pliny the Elder, instanceOf, Roman military officer]
-
A.
Roman military commander
chosen
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
-
B.
Roman soldier
A Roman soldier is a disciplined, heavily trained infantryman of ancient Rome’s military, equipped with standardized armor and weapons, who served to expand and protect the Roman state.
-
C.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
D.
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.
-
E.
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.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:57 p.m.