Triple
T2197585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stavka |
E50411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military high command |
C450
|
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: Soviet military high command Context triple: [Stavka, instanceOf, Soviet military high command]
-
A.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
B.
general of the army
chosen
A general of the army is the highest-ranking military officer responsible for overseeing large-scale strategic planning, command, and coordination of an entire nation's land forces.
-
C.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
D.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
E.
military reformer
A military reformer is an individual who critically evaluates existing armed forces structures, doctrines, and practices and implements innovative changes to improve their effectiveness, efficiency, and adaptability.
- F. None of above.
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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.