Triple
T2046681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tweebosch |
E45467
|
entity |
| Predicate | commander1Role |
P2084
|
FINISHED |
| Object | Koos de la Rey as Boer general |
—
|
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: Koos de la Rey as Boer general | Statement: [Battle of Tweebosch, commander1Role, Koos de la Rey as Boer general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commander1Role Context triple: [Battle of Tweebosch, commander1Role, Koos de la Rey as Boer general]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
-
C.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
-
D.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
E.
hasCommander
Indicates that one entity serves as the commanding officer or leader of 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.