Triple
T8924423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sextus Pompeius |
E212504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military leader |
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 leader Context triple: [Sextus Pompeius, instanceOf, Roman military leader]
-
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 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 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.
-
D.
Roman military office
A Roman military office is an administrative and command position within the Roman armed forces responsible for organizing, directing, and managing soldiers, resources, and military operations.
-
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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.