Triple
T30319918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Vipsanius Agrippa |
E771171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman admiral |
C45337
|
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 admiral Context triple: [Marcus Vipsanius Agrippa, instanceOf, Roman admiral]
-
A.
ancient Roman admiral
chosen
An ancient Roman admiral is a high-ranking naval commander responsible for leading Rome’s fleets in warfare, securing sea routes, and executing maritime strategies on behalf of the Republic or Empire.
-
B.
Roman military commander
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.
-
C.
Venetian admiral
A Venetian admiral is a high-ranking naval commander of the Republic of Venice responsible for leading its fleets, safeguarding maritime trade routes, and directing naval warfare in the Mediterranean and beyond.
-
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 proconsul
A Roman proconsul was a former consul granted extended imperium to govern a province, command armies, and administer justice on behalf 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:52 p.m.