Triple
T22205235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directorate of Emergency Services (USAG West Point) |
E548788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military emergency services directorate |
C13448
|
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 emergency services directorate Context triple: [Directorate of Emergency Services (USAG West Point), instanceOf, military emergency services directorate]
-
A.
civil emergency service
A civil emergency service is a public organization responsible for preparing for, responding to, and managing non-military crises and disasters to protect people, property, and the environment.
-
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.
military logistics directorate
A military logistics directorate is an organizational unit responsible for planning, coordinating, and managing the procurement, storage, movement, and maintenance of supplies, equipment, and services that sustain armed forces operations.
-
D.
military support organization
chosen
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
E.
military police command
A military police command is an organizational unit within the armed forces responsible for law enforcement, security operations, discipline, and order among military personnel and installations.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.