Triple
T19522030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kert campaign |
E488424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish military operation |
C37274
|
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: Spanish military operation Context triple: [Kert campaign, instanceOf, Spanish military operation]
-
A.
Spanish naval operation
A Spanish naval operation is a coordinated maritime mission conducted by Spain’s naval forces to achieve specific military, security, or strategic objectives at sea.
-
B.
Portuguese military campaign
A Portuguese military campaign is a coordinated series of armed operations conducted by Portugal’s military forces to achieve specific strategic, political, or territorial objectives, often within a defined geographic area and time period.
-
C.
Spanish Civil War battlefront
A Spanish Civil War battlefront is a geographically defined zone where Republican and Nationalist forces directly engaged in sustained military operations, including trenches, fortifications, and shifting lines of control.
-
D.
Reconquista campaign
A Reconquista campaign is a coordinated military and political effort by Christian kingdoms in medieval Iberia to reclaim territories under Muslim rule, typically involving prolonged warfare, shifting alliances, and religiously framed objectives.
-
E.
Spanish colonial war
chosen
A Spanish colonial war is an armed conflict involving Spain’s efforts to conquer, control, or defend overseas territories within its colonial empire, typically against indigenous populations, rival European powers, or independence movements.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:40 p.m.