Triple
T18522423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grigory Shtern |
E452620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Red Army commander |
C40547
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Red Army commander Context triple: [Grigory Shtern, instanceOf, Red Army commander]
-
A.
Russian field marshal
A Russian field marshal is the highest-ranking military officer in the Russian (historically Imperial or Soviet-equivalent) army, responsible for commanding large-scale operations and shaping overall military strategy.
-
B.
Soviet Air Defense Forces commander
A Soviet Air Defense Forces commander was a high-ranking military officer responsible for planning, directing, and coordinating the detection, interception, and destruction of hostile aerial threats within the airspace of the Soviet Union and its allies.
-
C.
Imperial Russian Army general
An Imperial Russian Army general is a high-ranking military officer of the Russian Empire responsible for commanding large formations, planning and directing operations, and implementing imperial military policy.
-
D.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
E.
Yugoslav military officer
A Yugoslav military officer is a commissioned member of the armed forces of the former Socialist Federal Republic of Yugoslavia, responsible for leading troops, planning and executing military operations, and upholding the doctrines and political-military objectives of the Yugoslav state.
- F. None of above. chosen
Provenance (1 batch)
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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.