Triple
T20606264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imatra railway station |
E506319
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Kouvola–Joensuu railway |
—
|
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: Kouvola–Joensuu railway | Statement: [Imatra railway station, railwayLine, Kouvola–Joensuu railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kouvola–Joensuu railway Context triple: [Imatra railway station, railwayLine, Kouvola–Joensuu railway]
-
A.
Oulu–Seinäjoki railway
The Oulu–Seinäjoki railway is a major rail line in western Finland that connects the northern city of Oulu with Seinäjoki, serving as an important route for both passenger and freight traffic.
-
B.
Jyväskylä–Äänekoski railway
The Jyväskylä–Äänekoski railway is a Finnish rail line connecting the city of Jyväskylä with the town of Äänekoski, serving both passenger and freight traffic in Central Finland.
-
C.
Tampere–Jyväskylä railway
The Tampere–Jyväskylä railway is a key Finnish rail line connecting the major inland cities of Tampere and Jyväskylä, serving both passenger and freight traffic through central Finland.
-
D.
Tampere–Pori railway
The Tampere–Pori railway is a Finnish rail line connecting the inland city of Tampere with the coastal city and port of Pori, serving both passenger and freight traffic in western Finland.
-
E.
Riihimäki–Tampere railway
The Riihimäki–Tampere railway is a major rail line in southern Finland that forms part of the main route between Helsinki and the city of Tampere, serving both passenger and freight 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: Kouvola–Joensuu railway Target entity description: The Kouvola–Joensuu railway is a major Finnish rail line in southeastern and eastern Finland that connects the city of Kouvola with Joensuu, serving both passenger and freight traffic.
-
A.
Oulu–Seinäjoki railway
The Oulu–Seinäjoki railway is a major rail line in western Finland that connects the northern city of Oulu with Seinäjoki, serving as an important route for both passenger and freight traffic.
-
B.
Jyväskylä–Äänekoski railway
The Jyväskylä–Äänekoski railway is a Finnish rail line connecting the city of Jyväskylä with the town of Äänekoski, serving both passenger and freight traffic in Central Finland.
-
C.
Tampere–Jyväskylä railway
The Tampere–Jyväskylä railway is a key Finnish rail line connecting the major inland cities of Tampere and Jyväskylä, serving both passenger and freight traffic through central Finland.
-
D.
Tampere–Pori railway
The Tampere–Pori railway is a Finnish rail line connecting the inland city of Tampere with the coastal city and port of Pori, serving both passenger and freight traffic in western Finland.
-
E.
Riihimäki–Tampere railway
The Riihimäki–Tampere railway is a major rail line in southern Finland that forms part of the main route between Helsinki and the city of Tampere, serving both passenger and freight traffic.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa2452888190858d273430cd783d |
completed | April 20, 2026, 10:35 p.m. |
Created at: April 16, 2026, 11:41 a.m.