Triple

T23127068
Position Surface form Disambiguated ID Type / Status
Subject Bokn E577059 entity
Predicate hasMainSettlement P2106 FINISHED
Object Føresvik 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: Føresvik | Statement: [Bokn, hasMainSettlement, Føresvik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Føresvik
Context triple: [Bokn, hasMainSettlement, Føresvik]
  • A. Føresvik chosen
    Føresvik is a small village in Rogaland county, Norway, serving as the main local hub on the island municipality of Bokn.
  • B. Fosnavåg
    Fosnavåg is a small coastal town in western Norway known for its maritime industries and scenic North Sea surroundings.
  • C. Fosnes
    Fosnes was a former rural municipality in Trøndelag county, Norway, known for its coastal landscape and small, dispersed population.
  • D. Gressvik
    Gressvik is a village in Fredrikstad Municipality in Viken county, Norway, located on the western side of the Glomma River.
  • E. Førde
    Førde is a town in western Norway known as a regional service center and cultural hub, particularly recognized for its annual folk music festival.
  • 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e55aa38819092816ffc52e20dbe completed April 29, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:59 p.m.