Triple

T20999364
Position Surface form Disambiguated ID Type / Status
Subject Levanger E517242 entity
Predicate hasRailwayStation P918 FINISHED
Object Levanger Station
Levanger Station is a railway station in the town of Levanger in Trøndelag county, Norway, serving as a stop on the Nordland Line.
 E1480018 NE FINISHED

How this triple was built (4 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: Levanger Station | Statement: [Levanger, hasRailwayStation, Levanger Station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Levanger Station
Context triple: [Levanger, hasRailwayStation, Levanger Station]
  • A. Verdal Station
    Verdal Station is a railway station in the town of Verdal in Trøndelag county, Norway, serving as a stop on the Nordland Line.
  • B. Vegårshei Station
    Vegårshei Station is a railway station in Vegårshei, Norway, serving as a local stop on the Sørlandet Line.
  • C. Alvdal Station
    Alvdal Station is a railway station serving the village of Alvdal in Innlandet county, Norway, on the Røros Line.
  • D. Støren Station
    Støren Station is a railway station in Trøndelag, Norway, serving as a junction where the Røros Line meets the Dovre Line and providing regional and long-distance train connections.
  • E. Brumunddal Station
    Brumunddal Station is a railway station serving the town of Brumunddal in Ringsaker, Innlandet county, Norway, on the Dovre Line.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Levanger Station
Triple: [Levanger, hasRailwayStation, Levanger Station]
Generated description
Levanger Station is a railway station in the town of Levanger in Trøndelag county, Norway, serving as a stop on the Nordland Line.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Levanger Station
Target entity description: Levanger Station is a railway station in the town of Levanger in Trøndelag county, Norway, serving as a stop on the Nordland Line.
  • A. Verdal Station
    Verdal Station is a railway station in the town of Verdal in Trøndelag county, Norway, serving as a stop on the Nordland Line.
  • B. Vegårshei Station
    Vegårshei Station is a railway station in Vegårshei, Norway, serving as a local stop on the Sørlandet Line.
  • C. Alvdal Station
    Alvdal Station is a railway station serving the village of Alvdal in Innlandet county, Norway, on the Røros Line.
  • D. Støren Station
    Støren Station is a railway station in Trøndelag, Norway, serving as a junction where the Røros Line meets the Dovre Line and providing regional and long-distance train connections.
  • E. Brumunddal Station
    Brumunddal Station is a railway station serving the town of Brumunddal in Ringsaker, Innlandet county, Norway, on the Dovre Line.
  • F. None of above. chosen

Provenance (5 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc2395108190871e173354e4ef6f completed April 21, 2026, 4:25 a.m.
NED1 Entity disambiguation (via context triple) batch_6a09ad4974688190a52fdccad3a29089 completed May 17, 2026, 11:58 a.m.
NEDg Description generation batch_6a09ae3744588190877e88dd38a80ebd completed May 17, 2026, 12:01 p.m.
NED2 Entity disambiguation (via description) batch_6a09af2184808190b42b5073e90bd83d completed May 17, 2026, 12:05 p.m.
Created at: April 16, 2026, 1:51 p.m.