Triple
T16384232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Army Center of Military History publications |
E397880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military history publication series |
C511
|
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 history publication series Context triple: [US Army Center of Military History publications, instanceOf, military history publication series]
-
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 publisher
A military publisher is an organization or entity that produces, edits, and distributes written, visual, or digital materials focused on military topics, including doctrine, history, strategy, technology, and training.
-
C.
history book series
chosen
A history book series is a collection of related volumes that chronologically or thematically explore past events, societies, and developments, often unified by a common author, approach, or narrative framework.
-
D.
military journal
A military journal is a periodical publication that documents, analyzes, and discusses military strategy, operations, technology, history, and policy for professional and academic audiences.
-
E.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
- 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.