Triple

T4741915
Position Surface form Disambiguated ID Type / Status
Subject Gudbrandsdalen E105262 entity
Predicate contains P35 FINISHED
Object Dovre E442846 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: Dovre | Statement: [Gudbrandsdalen, contains, Dovre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dovre
Context triple: [Gudbrandsdalen, contains, Dovre]
  • A. Dovre chosen
    Dovre is a mountainous municipality in Innlandet county, Norway, known for its rugged landscapes and proximity to Dovrefjell National Park.
  • B. Trysil
    Trysil is a Norwegian municipality renowned for its large alpine ski resort and extensive outdoor recreation opportunities.
  • C. Verdal
    Verdal is a municipality in central Norway known for its agricultural landscape, industrial activity, and the historic battlefield of Stiklestad.
  • D. Nordkjosbotn
    Nordkjosbotn is a small village in Troms county in northern Norway, known as a key road junction and service center where major routes connect inland and coastal regions.
  • E. Finnsnes
    Finnsnes is a small coastal town in northern Norway that serves as a commercial and transport hub for the island municipality of Senja.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a7153881909eac451fc7566d25 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69bec33b413081909cc7fcadd6997565 completed March 21, 2026, 4:11 p.m.
Created at: March 20, 2026, 1:19 p.m.