Triple
T4079399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman intervention of Pompey in 63 BCE |
E87440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political intervention |
C15185
|
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 political intervention Context triple: [Roman intervention of Pompey in 63 BCE, instanceOf, Roman political intervention]
-
A.
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.
-
B.
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.
-
C.
phase of the Roman Republic
A phase of the Roman Republic is a distinct historical period characterized by specific political structures, social dynamics, and key events that collectively shaped the evolution of Roman republican governance.
-
D.
military intervention
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
-
E.
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.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.