Triple
T31275571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Doctrine Publication 1 The Army |
E797506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | field manual successor publication |
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: field manual successor publication Context triple: [Army Doctrine Publication 1 The Army, instanceOf, field manual successor publication]
-
A.
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.
-
B.
military publication
A military publication is an official document or periodical produced by a military organization to communicate doctrine, policy, procedures, information, or analysis to service members and related stakeholders.
-
C.
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.
-
D.
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.
-
E.
U.S. Army pamphlet
A U.S. Army pamphlet is an official informational publication that provides guidance, reference material, or explanatory content to support Army policies, procedures, training, or 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.