Triple
T31275520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Publication 5-0, Joint Planning |
E797505
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military doctrinal manual |
C8923
|
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 doctrinal manual Context triple: [Joint Publication 5-0, Joint Planning, instanceOf, military doctrinal manual]
-
A.
military doctrine handbook
A military doctrine handbook is an authoritative manual that outlines the fundamental principles, strategies, tactics, and procedures guiding the planning and conduct of military operations.
-
B.
United States military manual
chosen
A United States military manual is an official publication that provides standardized doctrine, procedures, and guidance for the organization, training, and operations of U.S. armed forces.
-
C.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
D.
military doctrinal framework
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
-
E.
military doctrinal publication series
A military doctrinal publication series is an organized set of authoritative documents that systematically codify and communicate a military organization’s fundamental principles, concepts, and procedures for planning, conducting, and supporting operations.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:13 p.m.