Triple
T14127476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucilius Bassus |
E340070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman military commander |
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: ancient Roman military commander Context triple: [Lucilius Bassus, instanceOf, ancient Roman military commander]
-
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.
Carthaginian military commander
A Carthaginian military commander is a high-ranking officer from ancient Carthage responsible for planning and leading land or naval forces in campaigns, battles, and strategic defense of Carthaginian interests.
-
D.
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.
-
E.
ancient Greek military leader
An ancient Greek military leader is a high-ranking commander responsible for organizing, directing, and strategizing the actions of Greek city-state or coalition forces in warfare.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.