Triple
T16239886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ncome River |
E394212
|
entity |
| Predicate | battleOutcomeSide |
P15330
|
FINISHED |
| Object | Voortrekkers victory at Battle of Blood River |
—
|
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: Voortrekkers victory at Battle of Blood River | Statement: [Ncome River, battleOutcomeSide, Voortrekkers victory at Battle of Blood River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcomeSide Context triple: [Ncome River, battleOutcomeSide, Voortrekkers victory at Battle of Blood River]
-
A.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
C.
victoriousSide
chosen
Indicates which participant or group emerged as the winner in a competitive or conflict situation.
-
D.
partOfConflictOutcome
Indicates that one entity represents a specific component or aspect of the overall outcome of a conflict involving another entity.
-
E.
belligerentSideAfterCapture
Indicates the party or side that an entity belongs to after it has been captured in a conflict or competitive interaction.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455d5270819090171d4207223a28 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.