Triple
T14698061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthaginian campaigns in Hispania |
E345216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carthaginian military operation |
C35037
|
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: Carthaginian military operation Context triple: [Carthaginian campaigns in Hispania, instanceOf, Carthaginian military operation]
-
A.
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.
-
B.
battle of the First Punic War
A battle of the First Punic War is a specific military engagement fought between Rome and Carthage (and their allies) between 264 and 241 BCE, characterized by evolving naval and land tactics that shaped the course of Mediterranean power.
-
C.
Roman military campaign
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
D.
Punic War
The Punic War is a historical conflict between ancient Rome and Carthage, characterized by a series of three wars fought from 264 to 146 BCE for dominance over the western Mediterranean.
-
E.
Carthaginian institution
A Carthaginian institution is a formal or informal organizational structure, practice, or system that governed the political, economic, religious, or social life of ancient Carthage.
- F. None of above. chosen
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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.