Triple
T38407701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus internal logistics |
E901381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial logistics organization |
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: industrial logistics organization Context triple: [Airbus internal logistics, instanceOf, industrial logistics organization]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
industrial automation organization
An industrial automation organization is an entity that designs, implements, and maintains automated systems and technologies to optimize manufacturing and industrial processes.
-
E.
logistics training center
A logistics training center is a specialized facility that provides education and hands-on instruction in supply chain management, transportation, warehousing, and related operational skills to prepare individuals for careers in logistics and distribution.
- 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.