Triple
T37744075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Axe |
E940798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cape Frontier War |
C29844
|
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: Cape Frontier War Context triple: [War of the Axe, instanceOf, Cape Frontier War]
-
A.
Xhosa Wars
chosen
The Xhosa Wars were a series of nine frontier conflicts between the Xhosa peoples and European colonists in the Eastern Cape of South Africa from the late 18th to late 19th centuries, driven by competition over land, cattle, and political control.
-
B.
Xhosa War
The Xhosa War is a historical conflict between the Xhosa people and European colonial powers in South Africa, marked by a series of nine frontier wars from 1779 to 1879 over land, resources, and sovereignty.
-
C.
Caucasian War
The Caucasian War was a prolonged 19th-century conflict in which the Russian Empire fought to conquer and pacify the peoples of the North Caucasus, marked by fierce resistance, mass displacement, and significant cultural and demographic upheaval.
-
D.
battle of the Second Boer War
A battle of the Second Boer War is a military engagement fought between British (and imperial) forces and Boer republic commandos in South Africa between 1899 and 1902, characterized by a mix of conventional and guerrilla warfare over control of territory and political sovereignty.
-
E.
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.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.