Triple
T22558091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands and Germany |
E557738
|
entity |
| Predicate | haveMajorPortsAndHinterlandLinks |
P148654
|
FINISHED |
| Object | Port of Amsterdam–German hinterland |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Port of Amsterdam–German hinterland | Statement: [Netherlands and Germany, haveMajorPortsAndHinterlandLinks, Port of Amsterdam–German hinterland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port of Amsterdam–German hinterland Context triple: [Netherlands and Germany, haveMajorPortsAndHinterlandLinks, Port of Amsterdam–German hinterland]
-
A.
Amsterdam–Frankfurt
Amsterdam–Frankfurt is a major international high-speed rail route linking the Netherlands and Germany, serving as a key corridor for business and leisure travel between the two cities.
-
B.
Port of Dordrecht
The Port of Dordrecht is a Dutch inland and seaport serving as an important regional hub for cargo handling and industrial activities in and around the city of Dordrecht.
-
C.
Rhine–Meuse–Scheldt inland shipping corridor
The Rhine–Meuse–Scheldt inland shipping corridor is a major European waterway network linking the Rhine, Meuse, and Scheldt river basins to facilitate extensive inland freight transport across several countries.
-
D.
Port of Nijmegen
The Port of Nijmegen is an inland port in the Dutch city of Nijmegen that serves as an important logistics and transport hub along the River Waal.
-
E.
Amsterdam–IJsselmeer shipping route
The Amsterdam–IJsselmeer shipping route is a key inland waterway in the Netherlands that connects the city of Amsterdam with the IJsselmeer lake, facilitating both commercial and recreational vessel traffic.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Port of Amsterdam–German hinterland Target entity description: The Port of Amsterdam–German hinterland is a key freight corridor linking the Port of Amsterdam with industrial and commercial regions in Germany via inland waterways, rail, and road.
-
A.
Amsterdam–Frankfurt
Amsterdam–Frankfurt is a major international high-speed rail route linking the Netherlands and Germany, serving as a key corridor for business and leisure travel between the two cities.
-
B.
Port of Dordrecht
The Port of Dordrecht is a Dutch inland and seaport serving as an important regional hub for cargo handling and industrial activities in and around the city of Dordrecht.
-
C.
Rhine–Meuse–Scheldt inland shipping corridor
chosen
The Rhine–Meuse–Scheldt inland shipping corridor is a major European waterway network linking the Rhine, Meuse, and Scheldt river basins to facilitate extensive inland freight transport across several countries.
-
D.
Port of Nijmegen
The Port of Nijmegen is an inland port in the Dutch city of Nijmegen that serves as an important logistics and transport hub along the River Waal.
-
E.
Amsterdam–IJsselmeer shipping route
The Amsterdam–IJsselmeer shipping route is a key inland waterway in the Netherlands that connects the city of Amsterdam with the IJsselmeer lake, facilitating both commercial and recreational vessel traffic.
- F. None of above.
Provenance (2 batches)
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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
Created at: April 16, 2026, 8:52 p.m.