Triple
T3593333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjørundfjord |
E76077
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Storfjorden |
E396830
|
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: Storfjorden | Statement: [Hjørundfjord, connectedTo, Storfjorden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Storfjorden Context triple: [Hjørundfjord, connectedTo, Storfjorden]
-
A.
Storfjorden
chosen
Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
-
B.
Bjørnafjorden
Bjørnafjorden is a large fjord in western Norway known for its scenic coastal landscape and role as an important marine and transport corridor in Vestland county.
-
C.
Randsfjorden
Randsfjorden is one of Norway’s largest inland lakes, located in Eastern Norway and known for its elongated shape and surrounding forested landscapes.
-
D.
Granvinfjorden
Granvinfjorden is a small side fjord in Vestland county, Norway, branching off the larger Hardangerfjord and surrounded by steep mountainous terrain.
-
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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15bbbcc81908d6cf95f8e70c6ca |
completed | March 8, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b595e7d1e481909538deb06b6007a2 |
completed | March 14, 2026, 5:07 p.m. |
Created at: March 8, 2026, 3:22 p.m.