Triple
T33711956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kłuszyn |
E863764
|
entity |
| Predicate | commanderSideRussian |
P70146
|
FINISHED |
| Object | Dmitry Shuisky |
—
|
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: Dmitry Shuisky | Statement: [Battle of Kłuszyn, commanderSideRussian, Dmitry Shuisky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderSideRussian Context triple: [Battle of Kłuszyn, commanderSideRussian, Dmitry Shuisky]
-
A.
commanderSideRussia
chosen
Indicates that the commander is aligned with, fighting for, or acting on behalf of the Russian side in a conflict or military context.
-
B.
commanderForSovietSide
Indicates that an entity serves as a military commander representing or leading forces on the Soviet side in a conflict or operation.
-
C.
combatantRussianSide
Indicates that an entity participates as a combatant on the Russian side in a conflict or military engagement.
-
D.
sovietCommand
Indicates that one entity holds a position of command or authority within a Soviet military or governmental structure over another entity.
-
E.
SovietForceType
Indicates that the entity is classified as a type or category of Soviet military force.
- 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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 1:43 a.m.