Triple
T334897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koos de la Rey |
E6702
|
entity |
| Predicate | notableVictory |
P4779
|
FINISHED |
| Object | defeat of British forces at Tweebosch |
—
|
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: defeat of British forces at Tweebosch | Statement: [Koos de la Rey, notableVictory, defeat of British forces at Tweebosch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVictory Context triple: [Koos de la Rey, notableVictory, defeat of British forces at Tweebosch]
-
A.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
B.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
C.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
D.
notableAttempt
Indicates that an entity made a significant or noteworthy effort to perform or achieve another entity or outcome.
-
E.
victoryIn
chosen
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac641708190b85fa21368e5de8e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.