Triple
T17555733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Support Program |
E427585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistics support program |
C39103
|
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: logistics support program Context triple: [Service Support Program, instanceOf, logistics support program]
-
A.
military logistics software system
A military logistics software system is an integrated digital platform that plans, tracks, and optimizes the movement, supply, maintenance, and readiness of military resources across operations and theaters.
-
B.
logistics brigade
A logistics brigade is a military unit responsible for planning, coordinating, and executing the supply, transportation, maintenance, and support services needed to sustain combat and support forces.
-
C.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
-
D.
United States freight program
A United States freight program is a coordinated set of policies, investments, and initiatives designed to improve the efficiency, safety, capacity, and environmental performance of the nation’s freight transportation system across modes such as trucking, rail, maritime, and air cargo.
-
E.
logistics command
Logistics command is the organizational function responsible for planning, coordinating, and controlling the movement, supply, and maintenance of resources to ensure operational readiness and sustained support.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.