Triple
T17452713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koleje Dolnośląskie |
E424951
|
entity |
| Predicate | hasRouteThrough |
P4374
|
FINISHED |
| Object | Legnica – Wrocław line |
—
|
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: Legnica – Wrocław line | Statement: [Koleje Dolnośląskie, hasRouteThrough, Legnica – Wrocław line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Legnica – Wrocław line Context triple: [Koleje Dolnośląskie, hasRouteThrough, Legnica – Wrocław line]
-
A.
Poznań–Piła railway line
The Poznań–Piła railway line is a key rail route in western Poland connecting the regional capital Poznań with the city of Piła, serving both passenger and freight traffic.
-
B.
Warsaw–Kraków main line
The Warsaw–Kraków main line is a major Polish railway corridor connecting the capital city Warsaw with Kraków, serving as one of the country’s key passenger and freight routes.
-
C.
Katowice–Gliwice railway line
The Katowice–Gliwice railway line is a major rail route in southern Poland that connects the cities of Katowice and Gliwice within the Upper Silesian metropolitan area.
-
D.
Łódź–Ostrów Wielkopolski railway
The Łódź–Ostrów Wielkopolski railway is a regional rail line in central Poland connecting the city of Łódź with Ostrów Wielkopolski and serving as an important route for both passenger and freight traffic.
-
E.
Katowice–Bielsko-Biała railway line
The Katowice–Bielsko-Biała railway line is a major rail route in southern Poland connecting the regional capital Katowice with the city of Bielsko-Biała, serving both passenger and freight traffic in the Silesian 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: Legnica – Wrocław line Target entity description: The Legnica–Wrocław line is a key railway route in Lower Silesia, Poland, connecting the cities of Legnica and Wrocław and serving as an important regional commuter and intercity corridor.
-
A.
Poznań–Piła railway line
The Poznań–Piła railway line is a key rail route in western Poland connecting the regional capital Poznań with the city of Piła, serving both passenger and freight traffic.
-
B.
Warsaw–Kraków main line
The Warsaw–Kraków main line is a major Polish railway corridor connecting the capital city Warsaw with Kraków, serving as one of the country’s key passenger and freight routes.
-
C.
Katowice–Gliwice railway line
The Katowice–Gliwice railway line is a major rail route in southern Poland that connects the cities of Katowice and Gliwice within the Upper Silesian metropolitan area.
-
D.
Łódź–Ostrów Wielkopolski railway
The Łódź–Ostrów Wielkopolski railway is a regional rail line in central Poland connecting the city of Łódź with Ostrów Wielkopolski and serving as an important route for both passenger and freight traffic.
-
E.
Katowice–Bielsko-Biała railway line
The Katowice–Bielsko-Biała railway line is a major rail route in southern Poland connecting the regional capital Katowice with the city of Bielsko-Biała, serving both passenger and freight traffic in the Silesian 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513faa0c8190961cf504c459bf34 |
completed | April 19, 2026, 3:51 a.m. |
Created at: April 10, 2026, 5:47 a.m.