Triple

T15216565
Position Surface form Disambiguated ID Type / Status
Subject Fløibanen E363650 entity
Predicate namedAfter P63 FINISHED
Object Mount Fløyen E1143509 NE FINISHED

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: Mount Fløyen | Statement: [Fløibanen, namedAfter, Mount Fløyen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Fløyen
Context triple: [Fløibanen, namedAfter, Mount Fløyen]
  • A. Mount Fløyen chosen
    Mount Fløyen is a popular mountain and viewpoint overlooking the city of Bergen in Norway, known for its scenic hiking trails and panoramic city and fjord views.
  • B. Narvikfjellet
    Narvikfjellet is a Norwegian mountain and ski resort near Narvik, known for its scenic fjord views and opportunities for skiing and outdoor recreation.
  • C. Galdhøpiggen
    Galdhøpiggen is the highest mountain in Norway and Scandinavia, located in the Jotunheimen range.
  • D. Kolåstinden
    Kolåstinden is a prominent alpine peak in Norway’s Sunnmøre Alps, renowned among hikers and ski mountaineers for its steep slopes and panoramic fjord views.
  • E. Hodnefjell
    Hodnefjell is an island that forms part of the Finnøy archipelago in Norway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0076f90c481909989befe031a2cae completed April 15, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fee5ebb8d48190b4afc540da8e6a4b completed May 9, 2026, 7:44 a.m.
Created at: April 10, 2026, 3:11 a.m.