Triple
T33189913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvato Supply Chain Solutions |
E849573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supply chain management provider |
C55744
|
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: supply chain management provider Context triple: [Arvato Supply Chain Solutions, instanceOf, supply chain management provider]
-
A.
logistics provider
chosen
A logistics provider is an organization that plans, coordinates, and executes the efficient movement and storage of goods across the supply chain from origin to destination.
-
B.
supply chain operations wing
The supply chain operations wing is the organizational unit responsible for planning, coordinating, and executing end-to-end material, information, and logistics flows to ensure timely, cost-effective delivery of goods and services.
-
C.
Supplier
A Supplier is an entity that provides goods, services, or resources to an organization, typically under agreed terms of quality, price, and delivery.
-
D.
distribution company
A distribution company is a business entity that purchases products from manufacturers or suppliers and efficiently stores, manages, and delivers them to retailers, wholesalers, or end customers within a defined supply chain network.
-
E.
global distribution system provider
A global distribution system provider is a company that operates a computerized network enabling transactions between travel service suppliers (such as airlines, hotels, and car rental companies) and travel agencies or end customers worldwide.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.