Triple

T17627472
Position Surface form Disambiguated ID Type / Status
Subject Lötschberg railway line E429884 entity
Predicate passesThrough P225 FINISHED
Object Frutigen 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: Frutigen | Statement: [Lötschberg railway line, passesThrough, Frutigen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frutigen
Context triple: [Lötschberg railway line, passesThrough, Frutigen]
  • A. Frutigen chosen
    Frutigen is a municipality in the Bernese Oberland region of Switzerland, known for its alpine landscape and location in the Kander Valley.
  • B. Ruetz
    Ruetz is a river in the Stubai Valley of Tyrol, Austria, known for its alpine course through the Stubai Alps before joining the Sill River.
  • C. Stoos
    Stoos is a small car-free mountain village and ski resort in central Switzerland, known for its scenic alpine setting and steep funicular railway.
  • D. Vionnaz
    Vionnaz is a municipality in the canton of Valais in southwestern Switzerland, located in the Rhône valley near the Chablais region.
  • E. Hoëgne
    Hoëgne is a river in eastern Belgium that flows through the Ardennes region before joining the Vesdre.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dbe3a308190a818d04f1a9b15f7 completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.