Triple
T16546195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Russian War 1830–1831 |
E401947
|
entity |
| Predicate | keyRussianCommander |
P70146
|
FINISHED |
| Object | Hans Karl von Diebitsch |
—
|
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: Hans Karl von Diebitsch | Statement: [Polish–Russian War 1830–1831, keyRussianCommander, Hans Karl von Diebitsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyRussianCommander Context triple: [Polish–Russian War 1830–1831, keyRussianCommander, Hans Karl von Diebitsch]
-
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.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
ArmenianCommander
Indicates that an individual serves as a military commander associated with Armenia.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34562c30c81908d6318f359002ff2 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.