Triple
T19961200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdańsk Główny |
E479817
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Gdańsk–Nowy Port railway (historical) |
—
|
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: Gdańsk–Nowy Port railway (historical) | Statement: [Gdańsk Główny, railwayLine, Gdańsk–Nowy Port railway (historical)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gdańsk–Nowy Port railway (historical) Context triple: [Gdańsk Główny, railwayLine, Gdańsk–Nowy Port railway (historical)]
-
A.
Gdańsk–Gdynia railway
The Gdańsk–Gdynia railway is a key rail line in northern Poland that connects the major Baltic port cities of Gdańsk and Gdynia within the Tricity metropolitan area.
-
B.
Gdynia–Słupsk railway
The Gdynia–Słupsk railway is a key rail line in northern Poland that connects the port city of Gdynia with the city of Słupsk, serving both regional and intercity traffic along the Baltic coast.
-
C.
Gdańsk–Stargard railway
The Gdańsk–Stargard railway is a major rail line in northern Poland that connects the port city of Gdańsk with the inland city of Stargard, serving numerous regional and intercity routes.
-
D.
Gdynia–Hel railway
The Gdynia–Hel railway is a coastal rail line in northern Poland that connects the port city of Gdynia with the Hel Peninsula, serving popular seaside resorts and tourist destinations along the Baltic Sea.
-
E.
Gdynia–Kościerzyna railway line
The Gdynia–Kościerzyna railway line is a regional rail route in northern Poland connecting the coastal city of Gdynia with the inland town of Kościerzyna through the Pomeranian region.
- 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: Gdańsk–Nowy Port railway (historical) Target entity description: The Gdańsk–Nowy Port railway was a historic suburban rail line in Gdańsk, Poland, that connected the city center with its port district and played a key role in local passenger and freight transport before its closure.
-
A.
Gdańsk–Gdynia railway
The Gdańsk–Gdynia railway is a key rail line in northern Poland that connects the major Baltic port cities of Gdańsk and Gdynia within the Tricity metropolitan area.
-
B.
Gdynia–Słupsk railway
The Gdynia–Słupsk railway is a key rail line in northern Poland that connects the port city of Gdynia with the city of Słupsk, serving both regional and intercity traffic along the Baltic coast.
-
C.
Gdańsk–Stargard railway
The Gdańsk–Stargard railway is a major rail line in northern Poland that connects the port city of Gdańsk with the inland city of Stargard, serving numerous regional and intercity routes.
-
D.
Gdynia–Hel railway
The Gdynia–Hel railway is a coastal rail line in northern Poland that connects the port city of Gdynia with the Hel Peninsula, serving popular seaside resorts and tourist destinations along the Baltic Sea.
-
E.
Gdynia–Kościerzyna railway line
The Gdynia–Kościerzyna railway line is a regional rail route in northern Poland connecting the coastal city of Gdynia with the inland town of Kościerzyna through the Pomeranian region.
- F. None of above. chosen
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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:54 p.m.