Triple
T12790588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Force policy of the United States Marine Corps |
E305748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military organizational doctrine |
C31893
|
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: military organizational doctrine Context triple: [Total Force policy of the United States Marine Corps, instanceOf, military organizational doctrine]
-
A.
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.
-
B.
warfighting doctrine
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.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:30 p.m.