Triple
T16949180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DoD manuals |
E411140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Department of Defense document |
C1314
|
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: U.S. Department of Defense document Context triple: [DoD manuals, instanceOf, U.S. Department of Defense document]
-
A.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
B.
United States federal document
chosen
A United States federal document is an official record, form, publication, or communication created, issued, or maintained by a federal agency or branch of the U.S. government in the course of its authorized duties.
-
C.
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.
-
D.
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.
-
E.
NATO doctrine publication
A NATO doctrine publication is an official document that codifies agreed multinational principles, procedures, and guidance for planning and conducting allied military 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.