Triple
T33711957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kłuszyn |
E863764
|
entity |
| Predicate | commanderSideSwedish |
P147712
|
FINISHED |
| Object | Jacob De la Gardie |
—
|
NE NERFINISHED |
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: Jacob De la Gardie | Statement: [Battle of Kłuszyn, commanderSideSwedish, Jacob De la Gardie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderSideSwedish Context triple: [Battle of Kłuszyn, commanderSideSwedish, Jacob De la Gardie]
-
A.
combatantCommanderSweden
Indicates that the referenced entity serves as a commander of Swedish combatant forces in a conflict or military context.
-
B.
combatantSwedishSide
chosen
Indicates that an entity participated as a combatant on the Swedish side in a conflict or war.
-
C.
SwedishTacticalAdvantage
Indicates that Sweden holds a superior strategic or tactical position over another party in a given context or conflict.
-
D.
DanishCommander
Indicates that an individual holds or held a commanding military role associated with Denmark.
-
E.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 1:43 a.m.