Triple
T35518035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps Warfighting Publication on reconnaissance and security |
E1026471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | field manual |
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 Context triple: [Marine Corps Warfighting Publication on reconnaissance and security, instanceOf, field manual]
-
A.
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.
-
B.
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.
-
C.
instructional manual
An instructional manual is a structured document that provides step-by-step guidance, explanations, and reference information to help users correctly and safely operate, assemble, or understand a product, system, or process.
-
D.
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.
-
E.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.