Triple
T23351731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skarnsund Bridge |
E592930
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | Skarnsund strait |
—
|
NE NERFINISHED |
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: Skarnsund strait | Statement: [Skarnsund Bridge, crosses, Skarnsund strait]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skarnsund strait Context triple: [Skarnsund Bridge, crosses, Skarnsund strait]
-
A.
Gisundet strait
Gisundet strait is a narrow body of water in northern Norway that separates the island of Senja from the mainland.
-
B.
Skarnsundet
chosen
Skarnsundet is a narrow strait in Trøndelag, Norway, known for its strong tidal currents and the Skarnsund Bridge that spans it.
-
C.
Strelasund
Strelasund is a strait in the Baltic Sea separating the German island of Rügen from the mainland near the city of Stralsund.
-
D.
Karmsundet
Karmsundet is a narrow strait in Rogaland county, Norway, separating the island of Karmøy from the mainland and forming part of the historic sailing route along the Norwegian coast.
-
E.
Tjeldsundet
Tjeldsundet is a narrow strait in northern Norway that separates the islands of Hinnøya and Tjeldøya and connects the Ofotfjorden with the open sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1401748190b77df0a45c2aeebf |
completed | April 29, 2026, 5:41 a.m. |
Created at: April 17, 2026, 5:20 p.m.