Triple
T18145320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coventry International Hub |
E434373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistics and distribution center |
C34872
|
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 and distribution center Context triple: [Coventry International Hub, instanceOf, logistics and distribution center]
-
A.
storage and distribution system
A storage and distribution system is an integrated arrangement of facilities, equipment, and processes designed to efficiently receive, store, manage, and deliver goods or resources to their intended destinations.
-
B.
logistics network
chosen
A logistics network is an interconnected system of facilities, transportation modes, and information flows designed to efficiently move goods from origin to destination while optimizing cost, time, and service quality.
-
C.
vehicle distribution center
A vehicle distribution center is a facility where vehicles are received, stored, processed, and dispatched to dealerships or end customers as part of the supply chain.
-
D.
oil and gas logistics hub
A strategically located facility that coordinates the transportation, storage, handling, and distribution of oil and gas products across pipelines, marine, rail, and road networks to optimize supply chain efficiency and reliability.
-
E.
logistics module
A logistics module is a software component that manages the planning, execution, and tracking of the movement and storage of goods, information, and related resources across a supply chain.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.