Triple
T17705398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftwaffe training regulations |
E441417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military training doctrine |
C39559
|
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 training doctrine Context triple: [Luftwaffe training regulations, instanceOf, military training doctrine]
-
A.
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.
-
B.
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.
-
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
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.
military training institution
A military training institution is an organized establishment dedicated to educating, training, and preparing individuals for service in the armed forces through structured programs in physical fitness, discipline, tactics, and leadership.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:05 a.m.