Triple
T15014401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romsdal |
E377920
|
entity |
| Predicate | containsFjord |
P5879
|
FINISHED |
| Object | Eresfjorden |
E173697
|
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: Eresfjorden | Statement: [Romsdal, containsFjord, Eresfjorden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eresfjorden Context triple: [Romsdal, containsFjord, Eresfjorden]
-
A.
Storfjorden
Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
-
B.
Reinefjorden
Reinefjorden is a dramatic fjord in Norway’s Lofoten archipelago, renowned for its steep mountains, fishing villages, and iconic Arctic coastal scenery.
-
C.
Eresfjord
chosen
Eresfjord is a small village in Møre og Romsdal county in western Norway, situated at the end of the Eresfjorden and surrounded by steep mountains and scenic fjord landscapes.
-
D.
Eidsfjorden
Eidsfjorden is a Norwegian fjord known for its dramatic coastal scenery and traditional fishing communities.
-
E.
Beisfjorden
Beisfjorden is a fjord in Nordland county, Norway, known as an inner branch of the larger Ofotfjord near the town of Narvik.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7623c3c819092ca36b358b01842 |
completed | April 15, 2026, 12:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0035428e608190b8bb41dabda044d1 |
completed | May 10, 2026, 7:35 a.m. |
Created at: April 10, 2026, 2:55 a.m.