Triple
T38218206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Warfares doctrine |
E1010741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | psychological operations doctrine |
C39705
|
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: psychological operations doctrine Context triple: [Three Warfares doctrine, instanceOf, psychological operations doctrine]
-
A.
military doctrinal framework
chosen
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
-
B.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
C.
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.
-
D.
military training doctrine
A military training doctrine is a formalized set of principles, methods, and standards that guides how armed forces prepare personnel and units to plan, fight, and support operations effectively and consistently.
-
E.
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.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.