Triple
T3661587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stetind |
E77660
|
entity |
| Predicate | viewOver |
P17987
|
FINISHED |
| Object | Tysfjorden |
E439360
|
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: Tysfjorden | Statement: [Stetind, viewOver, Tysfjorden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tysfjorden Context triple: [Stetind, viewOver, Tysfjorden]
-
A.
Tysfjorden
chosen
Tysfjorden is a dramatic fjord in Nordland county, northern Norway, known for its steep mountains, deep waters, and scenic Arctic landscapes.
-
B.
Beisfjorden
Beisfjorden is a fjord in Nordland county, Norway, known as an inner branch of the larger Ofotfjord near the town of Narvik.
-
C.
Lysefjord
Lysefjord is a dramatic, steep-walled fjord in southwestern Norway, famed for its towering cliffs, including the iconic Preikestolen (Pulpit Rock), and striking natural scenery.
-
D.
Romsdalsfjorden
Romsdalsfjorden is a scenic fjord in Møre og Romsdal county, Norway, known for its dramatic landscapes, coastal towns, and role as a key waterway in the Romsdal region.
-
E.
Storfjorden
Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d826d88190b0b50e8592088a36 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b63702874881909610763d5a48b09d |
completed | March 15, 2026, 4:35 a.m. |
Created at: March 8, 2026, 3:25 p.m.