Triple
T10087467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Spion Kop |
E215256
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Spion Kop |
E841075
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Spion Kop | Statement: [Battle of Spion Kop, alsoKnownAs, Spion Kop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spion Kop Context triple: [Battle of Spion Kop, alsoKnownAs, Spion Kop]
-
A.
Spion Kop
chosen
Spion Kop is a prominent hill in KwaZulu-Natal, South Africa, best known as the site of a major and bloody battle during the Second Boer War.
-
B.
Paardeberg
Paardeberg was a key battle of the Second Boer War in 1900, where British and colonial forces encircled and forced the surrender of a major Boer army in South Africa.
-
C.
Salvokop Hill
Salvokop Hill is a prominent elevation in Pretoria, South Africa, known as the site of the national heritage complex Freedom Park.
-
D.
Piekberg
Piekberg is a low, wooded hill on the German island of Rügen, notable as its highest natural elevation.
-
E.
Magersfontein kopje
Magersfontein kopje is a prominent hill in South Africa notable as the central defensive position of Boer forces during the Second Boer War’s Battle of Magersfontein.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cbd822a08190841e51862e5e1e27 |
completed | April 5, 2026, 8:53 p.m. |
Created at: March 30, 2026, 9:01 p.m.