Triple
T16319191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochinchina campaign |
E396246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish colonial war |
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 colonial war Context triple: [Cochinchina campaign, instanceOf, Spanish colonial war]
-
A.
Cuban war of independence
The Cuban War of Independence (1895–1898) was the final and most significant Cuban uprising against Spanish colonial rule, culminating in U.S. intervention and the end of Spain’s empire in the Americas.
-
B.
Portuguese Colonial War
The Portuguese Colonial War was a series of armed conflicts from 1961 to 1974 between Portugal and independence movements in its African colonies—primarily Angola, Mozambique, and Guinea-Bissau—that ultimately led to the end of the Portuguese Empire.
-
C.
Mesoamerican war
Mesoamerican war is a conceptual class encompassing the organized, often ritualized armed conflicts among pre-Columbian Mesoamerican societies, characterized by distinctive military practices, religious motivations, and sociopolitical objectives.
-
D.
Frontier War
Frontier War is a prolonged, often low-intensity conflict that occurs along or beyond a political or cultural boundary, characterized by skirmishes, raids, and contested control of sparsely governed territories.
-
E.
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.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.