Triple
T10835294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern campaign of the Mexican War of Independence |
E255739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurgent campaign |
C3700
|
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: insurgent campaign Context triple: [Southern campaign of the Mexican War of Independence, instanceOf, insurgent campaign]
-
A.
armed uprising
An armed uprising is a collective, often organized rebellion in which a group uses weapons and force to challenge, resist, or overthrow an existing authority or government.
-
B.
guerrilla conflict
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
C.
irredentist campaign
An irredentist campaign is a coordinated political and often propagandistic effort by a state or movement to reclaim and incorporate territories it regards as historically or ethnically its own from another sovereign state.
-
D.
indigenous rebellion
Indigenous rebellion is a collective uprising by native or original inhabitants of a region against external domination, exploitation, or cultural suppression, often aiming to reclaim autonomy, land, and traditional ways of life.
-
E.
resistance movement
chosen
A resistance movement is an organized effort by a group of people to oppose, undermine, or overthrow an existing power, authority, or occupying force, often through political, social, or guerrilla actions.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.