Triple
T22070209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longtown MOD depot |
E545385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics site |
C45755
|
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 site Context triple: [Longtown MOD depot, instanceOf, military logistics site]
-
A.
military logistics enterprise
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.
-
B.
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.
-
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.
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.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.