Triple
T10985882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of De Klipdrift |
E259627
|
entity |
| Predicate | BoerForceType |
P6154
|
FINISHED |
| Object | highly mobile mounted commandos |
—
|
LITERAL 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: highly mobile mounted commandos | Statement: [Battle of De Klipdrift, BoerForceType, highly mobile mounted commandos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoerForceType Context triple: [Battle of De Klipdrift, BoerForceType, highly mobile mounted commandos]
-
A.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
B.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
C.
SovietForceType
Indicates that the entity is classified as a type or category of Soviet military force.
-
D.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
E.
BoerCasualties
Indicates the number or occurrence of casualties suffered by Boer forces in a conflict or engagement.
- F. None of above.
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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b2e4a88190a81504eee77e2298 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.