Triple
T22953493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ulundi |
E570085
|
entity |
| Predicate | tacticUsedByBritish |
P30685
|
FINISHED |
| Object | infantry square formation |
—
|
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: infantry square formation | Statement: [Battle of Ulundi, tacticUsedByBritish, infantry square formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByBritish Context triple: [Battle of Ulundi, tacticUsedByBritish, infantry square formation]
-
A.
militaryForceInvolved (British)
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
B.
strengthBritishForces
Indicates the numerical size or combat capacity of British military forces in a given context or operation.
-
C.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
-
D.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
E.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a34c30819099ff4812500a0991 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.