Triple
T16949035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle Staff Noncommissioned Officer Course |
E411137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle staff course |
C1577
|
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: battle staff course Context triple: [Battle Staff Noncommissioned Officer Course, instanceOf, battle staff course]
-
A.
military training directorate
The military training directorate is the organizational unit responsible for planning, coordinating, and overseeing all training programs, standards, and curricula for military personnel.
-
B.
military selection course
A military selection course is an intensive, highly structured program designed to evaluate and filter candidates for specialized military roles through rigorous physical, mental, and psychological challenges.
-
C.
U.S. Army school
chosen
A U.S. Army school is a military educational institution that provides specialized training and professional development to soldiers and Army personnel to prepare them for specific roles, missions, and leadership responsibilities.
-
D.
military education leadership position
A military education leadership position is a role responsible for directing, managing, and improving the training, professional development, and academic programs that prepare military personnel for effective service and leadership.
-
E.
special operations forces course
A special operations forces course is an intensive training program designed to develop elite military personnel in advanced combat skills, unconventional warfare, and high-risk mission execution.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.