Triple
T8737335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vercellae |
E207418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engagement of the Cimbrian War |
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: engagement of the Cimbrian War Context triple: [Battle of Vercellae, instanceOf, engagement of the Cimbrian War]
-
A.
engagement of the Italian Wars
An engagement of the Italian Wars is a specific military confrontation—ranging from pitched battles to sieges and skirmishes—fought between rival European powers and Italian states during the protracted conflicts over control of the Italian peninsula from 1494 to 1559.
-
B.
Illyrian revolt
The Illyrian revolt was a significant uprising by the Illyrian tribes against Roman rule in the early 1st century CE, challenging Roman authority in the western Balkans.
-
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.
engagement of the Nine Years' War
An engagement of the Nine Years' War is a specific military confrontation—such as a battle, siege, raid, or skirmish—fought between the war’s opposing coalitions within the broader 1688–1697 conflict.
-
E.
battle of the Italian Wars
A battle of the Italian Wars is a military engagement fought between 1494 and 1559 among major European powers over control of the Italian peninsula, typically involving shifting alliances, evolving tactics, and significant political consequences.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.