Triple
T32150771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Modular |
E821152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South African military operation |
C340
|
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: South African military operation Context triple: [Operation Modular, instanceOf, South African military operation]
-
A.
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.
-
B.
Argentine military operation
An Argentine military operation is a coordinated set of actions conducted by Argentina’s armed forces to achieve specific strategic, tactical, or security objectives, either domestically or abroad.
-
C.
Xhosa Wars
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.
-
D.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
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.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:31 a.m.