Triple

T22756637
Position Surface form Disambiguated ID Type / Status
Subject Bjerkvik E562860 entity
Predicate locatedNorthOf P305 FINISHED
Object Narvik town 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: Narvik town | Statement: [Bjerkvik, locatedNorthOf, Narvik town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narvik town
Context triple: [Bjerkvik, locatedNorthOf, Narvik town]
  • A. Narvik chosen
    Narvik is a port town in northern Norway known for its strategic importance during World War II and as the site of major naval and land battles.
  • B. Kiruna
    Kiruna is a mining town in northern Sweden known for its large iron ore mine and its location above the Arctic Circle.
  • C. Knarvik
    Knarvik is a village in Vestland county, Norway, known as a local commercial and service hub just north of Bergen.
  • D. Andenes
    Andenes is a small coastal village in northern Norway known for its Arctic location, fishing heritage, and whale-watching tourism.
  • E. Karasjok
    Karasjok is a municipality in northern Norway known as a cultural and political center for the Sámi people.
  • 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_69e24551ec7881909a9c924dbea155f6 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f179bd22588190ac724a656194f5b9 completed April 29, 2026, 3:23 a.m.
Created at: April 17, 2026, 3:25 p.m.