Triple
T30854875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal terminals |
E785892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime cargo terminal network |
C28493
|
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: maritime cargo terminal network Context triple: [Suez Canal terminals, instanceOf, maritime cargo terminal network]
-
A.
maritime cargo terminal
chosen
A maritime cargo terminal is a specialized facility at a seaport where ships are loaded and unloaded, and cargo is temporarily stored, sorted, and transferred between sea and land transportation modes.
-
B.
bulk cargo terminal
A bulk cargo terminal is a specialized port facility designed for the efficient handling, storage, and transfer of unpackaged bulk commodities such as coal, grain, ore, and fertilizers between ships, land transport, and storage areas.
-
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.
coal terminal
A coal terminal is a specialized facility at a port or rail hub designed for the receipt, storage, handling, and loading or unloading of coal for bulk transportation.
-
E.
ferry service network
A ferry service network is a coordinated system of water-based transport routes, vessels, terminals, and schedules that moves passengers and cargo between multiple ports or coastal locations.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:46 p.m.