Triple

T15216950
Position Surface form Disambiguated ID Type / Status
Subject Lærdalsøyri E363659 entity
Predicate hasNearbyInfrastructure P231 FINISHED
Object Lærdal Tunnel E421020 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: Lærdal Tunnel | Statement: [Lærdalsøyri, hasNearbyInfrastructure, Lærdal Tunnel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lærdal Tunnel
Context triple: [Lærdalsøyri, hasNearbyInfrastructure, Lærdal Tunnel]
  • A. Lærdal Tunnel chosen
    The Lærdal Tunnel is a 24.5-kilometer road tunnel in Norway, renowned as one of the world's longest road tunnels and a key link between Oslo and Bergen.
  • B. Honningsvåg Tunnel
    Honningsvåg Tunnel is a road tunnel in northern Norway that carries traffic along the E69 highway toward the North Cape.
  • C. Tromsøysund Tunnel
    Tromsøysund Tunnel is an undersea road tunnel in northern Norway that connects the island city of Tromsø to the mainland.
  • D. Oslo Tunnel
    The Oslo Tunnel is a central railway tunnel in Oslo, Norway, that carries most of the city's mainline train traffic between its principal stations.
  • E. Finnøy Tunnel
    The Finnøy Tunnel is an undersea road tunnel in Norway that connects the island of Finnøy to the mainland road network.
  • 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_69fed343f51481908f04c35d37b39ad2 completed May 9, 2026, 6:25 a.m.
Created at: April 10, 2026, 3:11 a.m.