Triple
T30627205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulu impi at the Battle of Isandlwana |
E779614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Zulu military force |
C58575
|
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: Zulu military force Context triple: [Zulu impi at the Battle of Isandlwana, instanceOf, Zulu military force]
-
A.
Zulu military regiment system
chosen
The Zulu military regiment system was an age-based, centrally organized structure that grouped warriors into disciplined, hierarchically commanded units (amabutho) for training, socialization, and coordinated warfare under the Zulu king.
-
B.
Boer commando unit
A Boer commando unit is a small, highly mobile, irregular military force of Boer fighters organized for guerrilla-style operations, typically mounted on horseback and operating with local autonomy.
-
C.
Air Force of Zimbabwe unit
An Air Force of Zimbabwe unit is an organizational subdivision of the Air Force of Zimbabwe, comprising personnel, aircraft, and equipment structured to perform specific operational, support, or training functions within the national air defense framework.
-
D.
Zulu war shield
A Zulu war shield is a large, oval, cowhide shield traditionally used by Zulu warriors for protection in battle and as a symbol of rank and identity.
-
E.
Arab volunteer force
The Arab volunteer force is a loosely organized group of individuals from various Arab countries who voluntarily join military or paramilitary efforts, often motivated by shared political, religious, or ideological goals rather than formal state directives.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:28 p.m.