Triple
T26990210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps publications |
E679844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military publication series |
C23745
|
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 publication series Context triple: [Marine Corps publications, instanceOf, military publication series]
-
A.
military doctrinal publication series
chosen
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.
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.
-
D.
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.
-
E.
naval doctrine publication series
A naval doctrine publication series is an organized collection of authoritative documents that codify a navy’s fundamental principles, tactics, procedures, and guidance for planning and conducting maritime 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:51 a.m.