Triple
T15751102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fauske |
E381845
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Skjerstad Fjord |
—
|
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: Skjerstad Fjord | Statement: [Fauske, locatedNear, Skjerstad Fjord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skjerstad Fjord Context triple: [Fauske, locatedNear, Skjerstad Fjord]
-
A.
Skjerstadfjorden
chosen
Skjerstadfjorden is a large fjord in Nordland county, Norway, known for its dramatic tidal currents and connection to the famous Saltstraumen maelstrom.
-
B.
Uskedalsfjorden
Uskedalsfjorden is a scenic fjord in Kvinnherad municipality in Vestland county, western Norway, known for its steep mountainsides and coastal landscapes.
-
C.
Storfjorden
Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
-
D.
Dalsfjorden
Dalsfjorden is a fjord in western Norway known for its steep surrounding mountains, deep waters, and small coastal settlements.
-
E.
Orkdalsfjorden
Orkdalsfjorden is a branch of the Trondheimsfjord in central Norway, known for its narrow, fjord-like extension inland toward the town of Orkanger.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05030e31081908c307a8dc7067db4 |
completed | April 16, 2026, 2:57 a.m. |
Created at: April 10, 2026, 4:47 a.m.