Triple
T29832377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Hendrik Roux |
E757558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boer War commandant |
C13343
|
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: Boer War commandant Context triple: [Paul Hendrik Roux, instanceOf, Boer War commandant]
-
A.
Boer military leader
chosen
A Boer military leader is a commander from the Dutch-descended Afrikaner communities of South Africa who directs and organizes Boer forces in military campaigns, often characterized by mobile, guerrilla-style warfare.
-
B.
Governor of the Cape Colony
The Governor of the Cape Colony was the British Crown’s chief executive and representative in the Cape of Good Hope, responsible for administering colonial government, implementing imperial policy, and overseeing relations with local populations.
-
C.
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.
-
D.
Belgian general
A Belgian general is a high-ranking military officer from Belgium responsible for leading large military formations, developing strategic plans, and overseeing operations within the Belgian Armed Forces or in multinational contexts.
-
E.
Dutch general
A Dutch general is a high-ranking military officer from the Netherlands responsible for leading and overseeing major army operations, strategy, and personnel.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:34 p.m.