Triple
T22502313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Klissow |
E556303
|
entity |
| Predicate | SwedishTacticalAdvantage |
P148482
|
FINISHED |
| Object | outmaneuvered larger enemy force |
—
|
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: outmaneuvered larger enemy force | Statement: [Battle of Klissow, SwedishTacticalAdvantage, outmaneuvered larger enemy force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SwedishTacticalAdvantage Context triple: [Battle of Klissow, SwedishTacticalAdvantage, outmaneuvered larger enemy force]
-
A.
combatantCommanderSweden
Indicates that the referenced entity serves as a commander of Swedish combatant forces in a conflict or military context.
-
B.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
C.
combatantSwedishSide
Indicates that an entity participated as a combatant on the Swedish side in a conflict or war.
-
D.
capturedGunsBySwedes
Indicates that guns were seized or taken into possession by Swedish forces from another party.
-
E.
armamentAdvantage
Indicates that one entity possesses a superior or more effective set of weapons or armaments compared to another entity.
- F. None of above. chosen
Provenance (4 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb6b47481909855fe93e95da7e7 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.