Triple
T31004315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Seaforth Container Terminal |
E790024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime freight hub |
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 freight hub Context triple: [Royal Seaforth Container Terminal, instanceOf, maritime freight hub]
-
A.
maritime trading centre
A maritime trading centre is a coastal hub where goods, services, and information are exchanged via sea routes, integrating port infrastructure, commercial activities, and logistics networks to facilitate regional and international trade.
-
B.
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.
-
C.
maritime warehouse
A maritime warehouse is a specialized storage facility located at or near a port, designed to handle, protect, and manage goods transported by sea, including loading, unloading, and temporary holding of cargo.
-
D.
inland port
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
E.
seaport
A seaport is a coastal facility equipped with harbors, docks, and infrastructure to enable the loading, unloading, storage, and transfer of cargo and passengers between sea and land transportation.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.