Triple
T31715179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob Prinsloo |
E809434
|
entity |
| Predicate | commandedForcesIn |
P155552
|
FINISHED |
| Object | Second Boer War |
—
|
NE NERFINISHED |
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: Second Boer War | Statement: [Jacob Prinsloo, commandedForcesIn, Second Boer War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedForcesIn Context triple: [Jacob Prinsloo, commandedForcesIn, Second Boer War]
-
A.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
B.
commandedForcesFrom
Indicates that one entity held command authority over military or organizational forces originating from another entity.
-
C.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
D.
commandedTroopsAt
chosen
Indicates that a person held command authority over military forces at a specific location or during a particular operation.
-
E.
occupationForcesCommandedBy
Indicates that a particular occupation force is under the command or authority of a specified commander or commanding 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 30, 2026, 11:17 p.m.