Triple

T22219459
Position Surface form Disambiguated ID Type / Status
Subject Trondheim Central Station E549169 entity
Predicate connectsTo P845 FINISHED
Object Storlien 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: Storlien | Statement: [Trondheim Central Station, connectsTo, Storlien]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Storlien
Context triple: [Trondheim Central Station, connectsTo, Storlien]
  • A. Storlien chosen
    Storlien is a village and ski resort in central Sweden near the Norwegian border, known for its winter sports and cross-border rail connections.
  • B. Støren
    Støren is a village in Trøndelag county, Norway, serving as a local commercial and transportation hub in the Gauldalen valley.
  • C. Storslett
    Storslett is a small village and administrative center in Nordreisa Municipality in Troms og Finnmark county in northern Norway.
  • D. Storvika
    Storvika is a small coastal settlement in the Tysfjorden area of Nordland county in northern Norway.
  • E. Blakstad
    Blakstad is a village in Agder county, Norway, known as the main local hub for services and administration in the surrounding Froland area.
  • 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_69e11e403d6481909a94d0aaf157f6ef completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b8edd288190a49f10e009122057 completed April 28, 2026, 9:50 p.m.
Created at: April 16, 2026, 8:37 p.m.