Triple
T13471867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storseisundet Bridge |
E311647
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Averøy |
E79229
|
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: Averøy | Statement: [Storseisundet Bridge, connects, Averøy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Averøy Context triple: [Storseisundet Bridge, connects, Averøy]
-
A.
Averøya
chosen
Averøya is a scenic Norwegian island known for its coastal landscapes and its location along the famous Atlantic Ocean Road in Western Norway.
-
B.
Andøy
Andøy is a municipality and island area in Nordland county, Norway, known for its Arctic landscapes, fishing communities, and whale-watching opportunities.
-
C.
Vesterøy
Vesterøy is one of the main inhabited islands in the Hvaler archipelago in southeastern Norway, known for its coastal landscapes and holiday cottages.
-
D.
Spjærøy
Spjærøy is one of the main inhabited islands in the Hvaler archipelago in southeastern Norway, known for its coastal scenery and holiday cottages.
-
E.
Storøya
Storøya is an island located in the lake Tyrifjorden 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf22e5f88190b1078f006c8ef7c0 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff677935408190a28af4cd34d82aa4 |
completed | May 9, 2026, 4:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.