Triple
T15885062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lærdal |
E385170
|
entity |
| Predicate | hasTunnel |
P21069
|
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ærdal, hasTunnel, Lærdal Tunnel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lærdal Tunnel Context triple: [Lærdal, hasTunnel, 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561997bc8190a40e7d68defbbddd |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb04598e0819094274868941195b9 |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.