Triple
T11848828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep operation |
E281854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military doctrine |
C626
|
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 doctrine Context triple: [Deep operation, instanceOf, Soviet military doctrine]
-
A.
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.
-
B.
warfighting doctrine
chosen
Warfighting doctrine is a formalized body of principles and concepts that guides how a military plans, organizes, and conducts operations to achieve strategic and tactical objectives in conflict.
-
C.
military strategy
Military strategy is the high-level planning and directing of armed forces and resources to achieve political and military objectives in war or conflict.
-
D.
Japanese imperial strategic doctrine
Japanese imperial strategic doctrine refers to the pre-1945 grand strategy that fused militarist nationalism, emperor-centered ideology, and expansionist aims to secure regional hegemony and resource self-sufficiency through aggressive war and colonial domination in East and Southeast Asia.
-
E.
U.S. Army doctrine
U.S. Army doctrine is the authoritative, evolving body of fundamental principles, tactics, techniques, and procedures that guides how the Army organizes, trains, and conducts operations across the range of military activities.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.