Triple
T32963074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Stormberg |
E843291
|
entity |
| Predicate | strengthBoer |
P6664
|
FINISHED |
| Object | approximately 2,000–2,500 burghers |
—
|
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 2,000–2,500 burghers | Statement: [Battle of Stormberg, strengthBoer, approximately 2,000–2,500 burghers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthBoer Context triple: [Battle of Stormberg, strengthBoer, approximately 2,000–2,500 burghers]
-
A.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
B.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
C.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
-
D.
strength
chosen
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
E.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
- 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.