Triple
T31219579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatsrand |
E795967
|
entity |
| Predicate | conflictSideAssociated |
P375
|
FINISHED |
| Object | Boer forces |
—
|
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: Boer forces | Statement: [Gatsrand, conflictSideAssociated, Boer forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictSideAssociated Context triple: [Gatsrand, conflictSideAssociated, Boer forces]
-
A.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
conflictSideContext
Indicates that an entity participates in a conflict on a particular side, within a specified contextual framing (such as time, place, or specific phase of the conflict).
-
C.
conflictRelation
Indicates a relationship in which two or more entities are in opposition, disagreement, or incompatibility, often involving competing goals, interests, or actions.
-
D.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
-
E.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:10 p.m.