Triple
T28411234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picentine War |
E719666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman war of expansion |
C11928
|
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 war of expansion Context triple: [Picentine War, instanceOf, Roman war of expansion]
-
A.
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.
-
B.
Italian Wars
The Italian Wars were a series of conflicts from 1494 to 1559 in which major European powers fought for control of the Italian peninsula, reshaping Renaissance politics, warfare, and diplomacy.
-
C.
Roman military campaign
chosen
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.
Greek expansion
Greek expansion refers to the historical process by which Greek culture, language, political influence, and settlements spread beyond the Greek mainland into the wider Mediterranean and Near Eastern regions through colonization, conquest, and trade.
-
E.
Roman–Dacian war
The Roman–Dacian war refers to the series of military conflicts between the Roman Empire and the Dacian Kingdom in the late 1st and early 2nd centuries AD, culminating in Rome’s conquest and annexation of Dacia under Emperor Trajan.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:27 a.m.