Triple
T23127035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokn |
E577059
|
entity |
| Predicate | hasCoastlineOn |
P212
|
FINISHED |
| Object | Karmsundet |
—
|
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: Karmsundet | Statement: [Bokn, hasCoastlineOn, Karmsundet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karmsundet Context triple: [Bokn, hasCoastlineOn, Karmsundet]
-
A.
Karmsundet
chosen
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.
-
B.
Nordsundet
Nordsundet is a strait in Norway spanned by the Nordsund Bridge, forming a marine passage between nearby islands or coastal areas.
-
C.
Norrsundet
Norrsundet is a small coastal locality in eastern Sweden known historically for its sawmill and harbor along the Gulf of Bothnia.
-
D.
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.
-
E.
Skarnsundet
Skarnsundet is a narrow strait in Trøndelag, Norway, known for its strong tidal currents and the Skarnsund Bridge that spans it.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e55aa38819092816ffc52e20dbe |
completed | April 29, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:59 p.m.