Triple
T35733347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainz–Ludwigshafen industrial ports |
E1032819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river port system |
C5917
|
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: river port system Context triple: [Mainz–Ludwigshafen industrial ports, instanceOf, river port system]
-
A.
inland port
chosen
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.
-
B.
waterway navigation system
A waterway navigation system is an integrated set of tools, sensors, and software that provides real-time guidance, routing, and safety information for vessels traveling on rivers, canals, and other inland or coastal waterways.
-
C.
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.
-
D.
port facility complex
A port facility complex is an integrated area of land and water with infrastructure, equipment, and services designed to support the berthing, loading, unloading, storage, and transfer of cargo and passengers between sea and land transport modes.
-
E.
port crane
A port crane is a large, fixed or mobile lifting machine used at harbors and container terminals to load, unload, and move cargo between ships and the shore.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.