Triple

T18627498
Position Surface form Disambiguated ID Type / Status
Subject Innherad E455320 entity
Predicate hasPart P35 FINISHED
Object Mosvik 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: Mosvik | Statement: [Innherad, hasPart, Mosvik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mosvik
Context triple: [Innherad, hasPart, Mosvik]
  • A. Mosvik chosen
    Mosvik was a former municipality in Trøndelag county, Norway, known for its rural landscape and coastal location along the Trondheimsfjord.
  • B. Malvik
    Malvik is a coastal municipality in central Norway, located in Trøndelag county near the city of Trondheim.
  • C. Håvik
    Håvik is a small coastal village located in Karmøy municipality in Rogaland county, southwestern Norway.
  • D. Vaksdal
    Vaksdal is a village in Vestland county, Norway, situated along the Veafjorden and known for its historic textile industry and railway connections.
  • E. Vedvik
    Vedvik is a small coastal village in the former Vågsøy municipality in Vestland county, western Norway.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f0581f0819083c1aba9fb85f6a7 completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.