Triple
T15528737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molde Airport, Årø |
E370152
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Molde Fjord |
E1416076
|
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: Molde Fjord | Statement: [Molde Airport, Årø, locatedNear, Molde Fjord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Molde Fjord Context triple: [Molde Airport, Årø, locatedNear, Molde Fjord]
-
A.
Molde Fjord
chosen
Molde Fjord is a Norwegian fjord near the town of Molde, known for its scenic coastal landscape and views of surrounding mountains and islands.
-
B.
Oslofjord
Oslofjord is a large inlet in southeastern Norway known for its islands, coastal towns, and role as the maritime gateway to Oslo.
-
C.
Strindfjorden
Strindfjorden is a bay-like arm of the Trondheimsfjord in central Norway, known for bordering parts of the city of Trondheim and its surrounding coastal landscape.
-
D.
Osafjorden
Osafjorden is a side fjord of Norway’s Hardangerfjord, known for its steep mountain scenery and tranquil, narrow waters.
-
E.
Mjøsund
Mjøsund is a small coastal settlement in northern Norway, situated on or near the island of Andørja and known for its scenic fjord landscape and maritime setting.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0843ce24748190a0bfca69e4d5006d |
completed | May 16, 2026, 10:15 a.m. |
Created at: April 10, 2026, 4:05 a.m.