Triple
T19394062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo Permanent Multipurpose Module |
E485141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Multipurpose Logistics Module |
C23178
|
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: Multipurpose Logistics Module Context triple: [Leonardo Permanent Multipurpose Module, instanceOf, Multipurpose Logistics Module]
-
A.
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.
-
B.
modular load-carrying system
A modular load-carrying system is a configurable assembly of interchangeable components designed to transport, support, and adapt to varying types and amounts of loads in different operational contexts.
-
C.
Functional Cargo Block
chosen
A Functional Cargo Block is a modular, self-contained unit designed to store, protect, and support the operation of integrated systems or equipment while enabling efficient transport, handling, and deployment.
-
D.
logistics code
A logistics code is a standardized identifier used to track, manage, and coordinate the movement, storage, and handling of goods and related operations across a supply chain.
-
E.
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.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:36 p.m.