Triple

T16197545
Position Surface form Disambiguated ID Type / Status
Subject Gudvangen E393104 entity
Predicate hasNearbyTunnel P29183 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: [Gudvangen, hasNearbyTunnel, Lærdal Tunnel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lærdal Tunnel
Context triple: [Gudvangen, hasNearbyTunnel, 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. Strynefjell Tunnel
    Strynefjell Tunnel is a road tunnel in Norway that carries traffic through the mountainous Strynefjell area along a key east–west route.
  • C. Honningsvåg Tunnel
    Honningsvåg Tunnel is a road tunnel in northern Norway that carries traffic along the E69 highway toward the North Cape.
  • D. Tromsøysund Tunnel
    Tromsøysund Tunnel is an undersea road tunnel in northern Norway that connects the island city of Tromsø to the mainland.
  • E. Nordhordland Tunnel
    The Nordhordland Tunnel is a subsea road tunnel in western Norway that connects the city of Bergen to the Nordhordland region as part of a major coastal highway route.
  • 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_69d87f1e49ac8190a311b54d32990576 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e222dc6b1c8190a3d8a6451ed8b95a completed April 17, 2026, 12:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a000ecf454081909660f4ab9c556ddc completed May 10, 2026, 4:51 a.m.
Created at: April 10, 2026, 5:02 a.m.