Triple
T22932585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force air mobility doctrine |
E569479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force 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: United States Air Force doctrine Context triple: [United States Air Force air mobility doctrine, instanceOf, United States Air Force doctrine]
-
A.
United States Air Force instruction
A United States Air Force instruction is an official, authoritative directive that establishes mandatory policies, procedures, and responsibilities for conducting specific activities within the Air Force.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:44 p.m.