Triple
T16049807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director Military Careers Administration |
E389323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military administrative authority |
C13719
|
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 administrative authority Context triple: [Director Military Careers Administration, instanceOf, military administrative authority]
-
A.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
-
B.
military administrative structure
A military administrative structure is the organized system of offices, roles, procedures, and chains of command that manage the planning, support, and governance of armed forces.
-
C.
military administrative corps
chosen
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.