Triple
T8234131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-3.4.9 Allied Joint Doctrine for Counterinsurgency |
E192362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military doctrinal document |
C626
|
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 doctrinal document Context triple: [AJP-3.4.9 Allied Joint Doctrine for Counterinsurgency, instanceOf, military doctrinal document]
-
A.
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.
-
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.
U.S. Army doctrine
U.S. Army doctrine is the authoritative, evolving body of fundamental principles, tactics, techniques, and procedures that guides how the Army organizes, trains, and conducts operations across the range of military activities.
-
D.
warfighting doctrine
chosen
Warfighting doctrine is a formalized body of principles and concepts that guides how a military plans, organizes, and conducts operations to achieve strategic and tactical objectives in conflict.
-
E.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.