Triple
T17556315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Deployment and Distribution Enterprise |
E427599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics enterprise |
C39108
|
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 logistics enterprise Context triple: [Joint Deployment and Distribution Enterprise, instanceOf, military logistics enterprise]
-
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.
Marine logistics group
A Marine logistics group is a military organization responsible for planning, coordinating, and executing the supply, maintenance, transportation, medical, and support services that sustain Marine forces in operations.
-
D.
logistics doctrine
Logistics doctrine is the overarching set of principles, policies, and standardized practices that guide how an organization plans, executes, and sustains the movement and support of resources to achieve its operational objectives.
-
E.
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.
- 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.