Triple
T32963076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Stormberg |
E843291
|
entity |
| Predicate | BritishPrisoners |
P6764
|
FINISHED |
| Object | approximately 600–700 captured |
—
|
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: approximately 600–700 captured | Statement: [Battle of Stormberg, BritishPrisoners, approximately 600–700 captured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishPrisoners Context triple: [Battle of Stormberg, BritishPrisoners, approximately 600–700 captured]
-
A.
prisonersOfWar
chosen
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
-
B.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
C.
shipOnBritishSide
Indicates that a ship is aligned with, operated by, or acting on behalf of the British side in a conflict or competitive context.
-
D.
UnionPrisonersTaken
Indicates that Union forces captured and held individuals as prisoners.
-
E.
prisonerOrigin
Indicates that a prisoner comes from, or is originally associated with, a specified place or source.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17b7a7c8190a00dd28fa8039a1c |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.