Triple
T1962662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Isandlwana |
E42620
|
entity |
| Predicate | BritishStrength |
P6664
|
FINISHED |
| Object | approximately 1,700 troops |
—
|
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 1,700 troops | Statement: [Battle of Isandlwana, BritishStrength, approximately 1,700 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishStrength Context triple: [Battle of Isandlwana, BritishStrength, approximately 1,700 troops]
-
A.
strength
chosen
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
B.
UnionStrength
Indicates the degree of solidarity, cohesion, and collective bargaining power within or among unions in a given context.
-
C.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
D.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
E.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.