Triple
T32714747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DoD Instruction 7045.7 |
E836491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DoD directive-type publication |
C57979
|
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: DoD directive-type publication Context triple: [DoD Instruction 7045.7, instanceOf, DoD directive-type publication]
-
A.
United States Army directive
A United States Army directive is an official, authoritative order or instruction issued by Army leadership that establishes or changes policy, procedures, responsibilities, or standards for the organization.
-
B.
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.
-
C.
NATO Allied Joint Publication
A NATO Allied Joint Publication is an official doctrinal document that provides standardized guidance and procedures for planning, conducting, and supporting joint and combined military operations among NATO member nations.
-
D.
United States military manual
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.
-
E.
NATO doctrinal publication
A NATO doctrinal publication is an official, collaboratively developed document that codifies agreed principles, procedures, and guidance for planning and conducting Alliance military operations and activities.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.