Triple

T20018158
Position Surface form Disambiguated ID Type / Status
Subject Rauma E494776 entity
Predicate hasRailway P848 FINISHED
Object Rauma Line NE NERFINISHED

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: Rauma Line | Statement: [Rauma, hasRailway, Rauma Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rauma Line
Context triple: [Rauma, hasRailway, Rauma Line]
  • A. Rauma Line chosen
    The Rauma Line is a scenic Norwegian railway route renowned for its dramatic mountain, river, and valley landscapes between Dombås and Åndalsnes.
  • B. Haparanda Line
    The Haparanda Line is a railway route in northern Sweden that connects to Finland, serving as an important cross-border transport link.
  • C. Grenaa Line
    Grenaa Line is a Danish railway route in Jutland that connects the city of Aarhus with the coastal town of Grenaa.
  • D. Saburtalo Line
    The Saburtalo Line is one of the main rapid transit lines of the Tbilisi Metro system in Tbilisi, Georgia, serving several central and residential districts of the city.
  • E. Saint Petersburg–Sortavala route
    The Saint Petersburg–Sortavala route is a regional transport corridor in northwestern Russia connecting the city of Saint Petersburg with the Karelian town of Sortavala, passing through intermediate localities such as Priozersk.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6623d76808190988990a8dc263ef7 completed April 20, 2026, 5:28 p.m.
Created at: April 11, 2026, 3:34 p.m.