Triple

T20999376
Position Surface form Disambiguated ID Type / Status
Subject Levanger E517242 entity
Predicate hasOfficialName P66 FINISHED
Object Levanger 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: Levanger | Statement: [Levanger, hasOfficialName, Levanger]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Levanger
Context triple: [Levanger, hasOfficialName, Levanger]
  • A. Levanger chosen
    Levanger is a historic town and municipality in Trøndelag county, Norway, known for its traditional wooden architecture and role as a regional commercial and educational center.
  • B. Leikanger
    Leikanger is a village and former municipality in Vestland county, Norway, situated along the Sognefjord and known for its fruit farming and scenic fjord landscape.
  • C. Slemdal
    Slemdal is a residential neighborhood in the Vestre Aker borough of Oslo, Norway, known for its green surroundings and affluent character.
  • D. Lørenskog
    Lørenskog is a suburban municipality in Viken county, Norway, located just east of Oslo and known for its residential areas and commercial centers.
  • E. Tvedestrand
    Tvedestrand is a coastal town and municipality in southern Norway known for its wooden houses, maritime heritage, and picturesque archipelago.
  • 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc2395108190871e173354e4ef6f completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:51 p.m.