Triple
T8465338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokushin-ron |
E200147
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese 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: Japanese military doctrine Context triple: [Hokushin-ron, instanceOf, Japanese military doctrine]
-
A.
Japanese government doctrine
Japanese government doctrine refers to the evolving set of principles, legal interpretations, and policy norms that guide Japan’s constitutional governance, security policy, and administrative decision-making within the framework of its pacifist constitution and parliamentary democracy.
-
B.
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.
-
C.
Imperial Japanese Army institution
An Imperial Japanese Army institution is an organizational entity—such as a school, bureau, or research center—established to train personnel, develop doctrine, manage logistics, or support the operational and administrative functions of the Imperial Japanese Army.
-
D.
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.
-
E.
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.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:11 p.m.