Triple
T32845390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusitanian War |
E840084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Republican war |
C61330
|
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 Republican war Context triple: [Lusitanian War, instanceOf, Roman Republican war]
-
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.
internal conflict of the Roman Republic
The internal conflict of the Roman Republic refers to the escalating social, political, and military struggles—among classes, factions, and ambitious leaders—that destabilized its institutions and ultimately transformed it into an autocratic empire.
-
C.
Roman battle
A Roman battle is a large-scale military engagement in which Roman forces, often organized into legions and auxiliaries, confront enemy armies using disciplined formations, tactical maneuvers, and a combination of infantry, cavalry, and siege weaponry.
-
D.
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.
-
E.
Third Servile War
The Third Servile War was a major slave uprising against the Roman Republic (73–71 BCE), led by the gladiator Spartacus, which challenged Roman authority in Italy before being brutally suppressed.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.