Triple

T17011502
Position Surface form Disambiguated ID Type / Status
Subject M1 line E412710 entity
Predicate hasStation P35 FINISHED
Object Ruoholahti station E429105 NE FINISHED

How this triple was built (2 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: Ruoholahti station | Statement: [M1 line, hasStation, Ruoholahti station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruoholahti station
Context triple: [M1 line, hasStation, Ruoholahti station]
  • A. Ruoholahti station chosen
    Ruoholahti station is an underground Helsinki Metro station serving the Ruoholahti district as a key western terminus and transport hub in the city’s metro network.
  • B. Kivenlahti station
    Kivenlahti station is a western endpoint of the Helsinki Metro system serving the Kivenlahti district in Espoo, Finland.
  • C. Mellunmäki station
    Mellunmäki station is an eastern Helsinki Metro station in the Mellunmäki district, notable for being one of the metro system’s outermost endpoints.
  • D. Matinkylä station
    Matinkylä station is a metro station in the Espoo district of Matinkylä that serves as a key western endpoint of the Helsinki Metro system.
  • E. Käppala station
    Käppala station is a stop on Stockholm’s Lidingöbanan light rail line serving the Käppala area on the island of Lidingö, Sweden.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d886cc4170819093deddc7b8b4b6a7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d47cc17c819087f7bd27582bcbfa completed April 18, 2026, 6:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b46e89c81908271eb22b535c558 completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:33 a.m.