Triple
T30767495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army casualty assistance officer program |
E783414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military support program |
C10566
|
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 support program Context triple: [U.S. Army casualty assistance officer program, instanceOf, military support program]
-
A.
military program
chosen
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
B.
military assistance program
A military assistance program is an organized initiative through which one nation or entity provides training, equipment, funding, or advisory support to strengthen the defense capabilities of another.
-
C.
logistics support program
A logistics support program is a coordinated set of processes, resources, and tools designed to plan, manage, and sustain the efficient movement, storage, and maintenance of materials and services throughout their lifecycle.
-
D.
military program category
A military program category is a classification grouping related defense initiatives, projects, or activities based on their purpose, function, or capability area within an armed forces structure.
-
E.
military support organization
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.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.