Triple

T19778954
Position Surface form Disambiguated ID Type / Status
Subject Tampere Central Station E475081 entity
Predicate railwayLine P848 FINISHED
Object Tampere–Jyväskylä 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: Tampere–Jyväskylä railway | Statement: [Tampere Central Station, railwayLine, Tampere–Jyväskylä railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Tampere–Jyväskylä railway
Context triple: [Tampere Central Station, railwayLine, Tampere–Jyväskylä railway]
  • A. 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.
  • B. Helsinki–Tampere railway
    The Helsinki–Tampere railway is a major Finnish rail line connecting the capital Helsinki with the city of Tampere, serving as one of the country’s busiest passenger and freight corridors.
  • C. 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.
  • D. Haapamäki–Jyväskylä railway
    The Haapamäki–Jyväskylä railway is a Finnish rail line in Central Finland that connects the town of Haapamäki with the city of Jyväskylä, serving both passenger and freight traffic.
  • E. Jyväskylä–Pieksämäki railway
    The Jyväskylä–Pieksämäki railway is a Finnish rail line in Central Finland that connects the city of Jyväskylä with Pieksämäki, 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: Tampere–Jyväskylä railway
Target entity description: 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.
  • A. 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.
  • B. Helsinki–Tampere railway
    The Helsinki–Tampere railway is a major Finnish rail line connecting the capital Helsinki with the city of Tampere, serving as one of the country’s busiest passenger and freight corridors.
  • C. 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.
  • D. Haapamäki–Jyväskylä railway
    The Haapamäki–Jyväskylä railway is a Finnish rail line in Central Finland that connects the town of Haapamäki with the city of Jyväskylä, serving both passenger and freight traffic.
  • E. Jyväskylä–Pieksämäki railway
    The Jyväskylä–Pieksämäki railway is a Finnish rail line in Central Finland that connects the city of Jyväskylä with Pieksämäki, 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6538230488190b45cd8aaec658f7f completed April 20, 2026, 4:25 p.m.
Created at: April 10, 2026, 1:49 p.m.