Triple
T20666426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkanger |
E507899
|
entity |
| Predicate | hasHarbour |
P3007
|
FINISHED |
| Object | Orkanger harbour |
—
|
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: Orkanger harbour | Statement: [Orkanger, hasHarbour, Orkanger harbour]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orkanger harbour Context triple: [Orkanger, hasHarbour, Orkanger harbour]
-
A.
Norheimsund harbour
Norheimsund harbour is a small coastal port in Norheimsund, Norway, serving as a local hub for maritime traffic, tourism, and access to the Hardangerfjord.
-
B.
Orkdal Harbor
chosen
Orkdal Harbor is a local port facility in Orkland municipality in Trøndelag, Norway, serving regional maritime transport and industry.
-
C.
Honningsvåg harbour
Honningsvåg harbour is a small Arctic port in northern Norway that serves as a key stop for coastal shipping and cruise vessels visiting the North Cape region.
-
D.
Fosnavåg harbour
Fosnavåg harbour is a coastal port in the town of Fosnavåg in Herøy, Møre og Romsdal, Norway, serving as an important hub for fishing, maritime services, and local industry.
-
E.
Brekstad harbour
Brekstad harbour is a coastal port facility in Brekstad, Norway, serving local maritime traffic, fishing, and regional transport connections.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c39dd48190965d65537592aef6 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.