Triple

T18113346
Position Surface form Disambiguated ID Type / Status
Subject Lunner E433535 entity
Predicate hasRailway P848 FINISHED
Object Gjøvik 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: Gjøvik Line | Statement: [Lunner, hasRailway, Gjøvik Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gjøvik Line
Context triple: [Lunner, hasRailway, Gjøvik Line]
  • A. Gjøvik Line chosen
    The Gjøvik Line is a Norwegian railway route connecting Oslo with the town of Gjøvik through the inland districts north of the capital.
  • B. Trønderbanen
    Trønderbanen is a regional railway line in Trøndelag, Norway, providing passenger train services that connect Trondheim with surrounding towns and communities.
  • C. Vy Gjøvikbanen
    Vy Gjøvikbanen is a Norwegian railway company that operates passenger train services on the Gjøvik Line as part of the Vy transport group.
  • D. Drammen Line
    The Drammen Line is a major Norwegian railway route connecting Oslo with the city of Drammen and serving as an important commuter and intercity corridor in the Oslo region.
  • E. Roa–Hønefoss Line
    The Roa–Hønefoss Line is a Norwegian railway line that connects the Bergen Line to the Gjøvik Line, serving as an important link between eastern and western Norway.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd3fd9c81909bfe95927f7553e3 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:28 a.m.