Triple
T28009466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitry Dokhturov |
E707374
|
entity |
| Predicate | roleInBattleOfBorodino |
P28183
|
FINISHED |
| Object | commanded the 6th Infantry Corps |
—
|
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: commanded the 6th Infantry Corps | Statement: [Dmitry Dokhturov, roleInBattleOfBorodino, commanded the 6th Infantry Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfBorodino Context triple: [Dmitry Dokhturov, roleInBattleOfBorodino, commanded the 6th Infantry Corps]
-
A.
roleInBattleOfGravelotte
Indicates the specific role or participation an entity had in the Battle of Gravelotte.
-
B.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
roleDuringRussianCivilWar
Indicates the specific function, position, or involvement an entity had during the period of the Russian Civil War.
-
D.
sideInRussianCivilWar
Indicates the faction or side that an entity supported or belonged to during the Russian Civil War.
-
E.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 8:02 p.m.