Triple
T26672446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ystad–Świnoujście ferry route |
E672370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Baltic Sea transport corridor |
C49884
|
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: Baltic Sea transport corridor Context triple: [Ystad–Świnoujście ferry route, instanceOf, Baltic Sea transport corridor]
-
A.
Baltic Sea port
A Baltic Sea port is a maritime facility located along the Baltic Sea coastline that provides infrastructure and services for the loading, unloading, storage, and transit of goods and passengers between sea and land transport.
-
B.
arm of the Baltic Sea
A narrow extension or inlet of the Baltic Sea that penetrates into the surrounding land or connects to adjacent bodies of water.
-
C.
trans-European transport network route
chosen
A trans-European transport network route is a designated corridor within the EU-wide integrated transport system that connects key cities, ports, and regions across Europe to facilitate efficient, interoperable, and sustainable cross-border movement of people and goods.
-
D.
federal highway of Russia
A federal highway of Russia is a major national roadway that forms part of the country’s primary transport network, connecting key cities, regions, and borders under federal jurisdiction and maintenance.
-
E.
Arctic port
An Arctic port is a maritime facility located within or near the Arctic Circle that supports the docking, loading, unloading, and servicing of vessels operating in polar conditions, often adapted for ice navigation and extreme weather.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:13 a.m.