Triple
T8387085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-5 Allied Joint Doctrine for Operational-Level Planning |
E197842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operational-level planning doctrine |
C3532
|
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: operational-level planning doctrine Context triple: [AJP-5 Allied Joint Doctrine for Operational-Level Planning, instanceOf, operational-level planning doctrine]
-
A.
operational concept
An operational concept is a high-level description of how a system, organization, or capability is intended to function in practice to achieve its objectives within a specific context.
-
B.
military planning document
chosen
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
C.
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.
-
D.
leadership doctrine
Leadership doctrine is a formalized set of principles, beliefs, and guidelines that shapes how leaders think, decide, and act within an organization or community.
-
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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.