Triple
T16384233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Army Center of Military History publications |
E397880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official U.S. Army publication |
C5132
|
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: official U.S. Army publication Context triple: [US Army Center of Military History publications, instanceOf, official U.S. Army publication]
-
A.
U.S. Army pamphlet
chosen
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.
-
B.
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.
-
C.
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.
-
D.
British Army doctrine publication
A British Army doctrine publication is an official document that articulates the Army’s authoritative principles, concepts, and guidance for the conduct of operations and training.
-
E.
United States Army regulation
A United States Army regulation is an official, binding directive issued by the Department of the Army that prescribes policies, responsibilities, and procedures governing the organization, operations, and conduct of Army personnel and 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.