Triple
T14971297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ullensvang |
E373324
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Hardanger Bridge |
E371911
|
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: Hardanger Bridge | Statement: [Ullensvang, hasPart, Hardanger Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hardanger Bridge Context triple: [Ullensvang, hasPart, Hardanger Bridge]
-
A.
Hardanger Bridge
chosen
Hardanger Bridge is one of Norway’s longest suspension bridges, spanning the Hardangerfjord to connect the regions of Ulvik and Ullensvang.
-
B.
Sotra Bridge
Sotra Bridge is a major suspension bridge in western Norway that links the island of Sotra to the mainland near Bergen.
-
C.
Lysaker Bridge
Lysaker Bridge is a key road and rail bridge in the Oslo area of Norway, carrying major traffic across the Lysaker River between Oslo and Bærum.
-
D.
Beisfjord Bridge
Beisfjord Bridge is a road bridge in Narvik, Norway, that spans the Beisfjorden and forms part of the key transport route in the region.
-
E.
Tromsø Bridge
Tromsø Bridge is an iconic cantilever road bridge in Tromsø, Norway, known for connecting the island of Tromsøya to the mainland and for its striking Arctic scenery.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e59a7c8190a1634a706ea68fda |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe8be6ce68819099f841d83c6ca33d |
completed | May 9, 2026, 1:20 a.m. |
Created at: April 10, 2026, 2:50 a.m.