Triple
T38407699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus internal logistics |
E901381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-house logistics operation |
C14224
|
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: in-house logistics operation Context triple: [Airbus internal logistics, instanceOf, in-house logistics operation]
-
A.
logistical operation
chosen
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.
-
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.
logistics network
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.
-
D.
logistics platform
A logistics platform is a digital system that coordinates, optimizes, and tracks the end-to-end movement of goods, data, and related services across supply chain participants.
-
E.
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.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.