Triple
T11640073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tromsø Bridge |
E276635
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Tromsøya |
E276624
|
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: Tromsøya | Statement: [Tromsø Bridge, connects, Tromsøya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tromsøya Context triple: [Tromsø Bridge, connects, Tromsøya]
-
A.
Tromøya
Tromøya is a large island off Norway’s southern coast, known for its scenic landscapes and proximity to the town of Arendal.
-
B.
Hamarøy
Hamarøy is a coastal municipality in Nordland county, Norway, known for its dramatic fjord and mountain landscapes and its association with author Knut Hamsun.
-
C.
Tromsøya island
chosen
Tromsøya island is a Norwegian island in Troms og Finnmark county that hosts the city center of Tromsø and is known for its Arctic location and vibrant cultural life.
-
D.
Tjeldøya
Tjeldøya is an island in northern Norway known for its rugged coastal landscape and location within the Ofoten region.
-
E.
Andøya
Andøya is a large Norwegian island in Nordland county, known for its dramatic coastal landscapes, space center, and rich bird and whale-watching opportunities.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f08fa01ba88190a4fa5a74fe96cfa9 |
completed | April 28, 2026, 10:44 a.m. |
Created at: April 8, 2026, 9:39 p.m.