Triple
T30670497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont battlefield |
E780779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Second Boer War site |
C16280
|
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: Second Boer War site Context triple: [Belmont battlefield, instanceOf, Second Boer War site]
-
A.
battle of the Second Boer War
chosen
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.
-
B.
World War I site
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
C.
Zulu cultural site
A Zulu cultural site is a location that preserves, practices, and showcases the traditions, history, and daily life of the Zulu people through architecture, rituals, performances, and community activities.
-
D.
historical Boer republic
A historical Boer republic is a 19th- to early 20th-century self-governing state established in southern Africa by Dutch-speaking settlers (Boers) seeking political independence from British colonial rule.
-
E.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:31 p.m.