Triple
T19680600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Instruction 36-2132 |
E472574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force instruction |
C42334
|
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 instruction Context triple: [Air Force Instruction 36-2132, instanceOf, United States Air Force instruction]
-
A.
United States Army directive
A United States Army directive is an official, authoritative order or instruction issued by Army leadership that establishes or changes policy, procedures, responsibilities, or standards for the organization.
-
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. Air Force course
A U.S. Air Force course is a structured program of military education or training designed to develop specific skills, knowledge, and competencies required for Air Force roles and missions.
-
D.
United States Army regulation
A United States Army regulation is an official, binding directive issued by the Department of the Army that prescribes policies, responsibilities, and procedures governing the organization, operations, and conduct of Army personnel and activities.
-
E.
NATO Allied Joint Publication
A NATO Allied Joint Publication is an official doctrinal document that provides standardized guidance and procedures for planning, conducting, and supporting joint and combined military operations among NATO member nations.
- F. None of above. chosen
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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:45 p.m.