Triple

T15889734
Position Surface form Disambiguated ID Type / Status
Subject Harstad harbour E385283 entity
Predicate hasLocalName P6353 FINISHED
Object Harstad havn E385283 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: Harstad havn | Statement: [Harstad harbour, hasLocalName, Harstad havn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harstad havn
Context triple: [Harstad harbour, hasLocalName, Harstad havn]
  • A. Harstad harbour chosen
    Harstad harbour is a coastal port area in the town of Harstad in northern Norway, serving as a hub for local maritime traffic, fishing, and Hurtigruten coastal express ships.
  • B. Orkdal Harbor
    Orkdal Harbor is a local port facility in Orkland municipality in Trøndelag, Norway, serving regional maritime transport and industry.
  • C. Haugesund harbor
    Haugesund harbor is a coastal port in western Norway that serves as a key maritime hub for the town of Haugesund and the surrounding region.
  • D. Bodø Harbour
    Bodø Harbour is a key coastal port in the Norwegian town of Bodø, serving as an important hub for regional shipping, fishing, and ferry traffic in northern Norway.
  • E. Melbu harbor
    Melbu harbor is a coastal port and ferry terminal village in Hadsel Municipality in Nordland county, Norway, serving as a local hub for maritime transport and fishing.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1561d5c28819094c3541d917a4433 completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb047b6248190b6c11ef20636f50f completed May 9, 2026, 10:08 p.m.
Created at: April 10, 2026, 4:51 a.m.