Triple
T25094606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO supply routes (historical) |
E628554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics network |
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 network Context triple: [NATO supply routes (historical), instanceOf, military logistics network]
-
A.
military logistics site
A military logistics site is a secured facility where armed forces coordinate, store, and distribute supplies, equipment, and transportation resources to support operations and readiness.
-
B.
military logistics enterprise
chosen
A military logistics enterprise is an organization that plans, coordinates, and executes the procurement, transportation, storage, and distribution of resources to ensure armed forces are supplied and operationally ready.
-
C.
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.
-
D.
military logistics problem
A military logistics problem involves planning, coordinating, and optimizing the movement, supply, and maintenance of forces and equipment to ensure operational readiness and effectiveness under resource, time, and environmental constraints.
-
E.
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.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:24 a.m.