Triple

T15091974
Position Surface form Disambiguated ID Type / Status
Subject Eidsvoll municipality E360441 entity
Predicate contains P35 FINISHED
Object Minnesund E333330 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: Minnesund | Statement: [Eidsvoll municipality, contains, Minnesund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minnesund
Context triple: [Eidsvoll municipality, contains, Minnesund]
  • A. Minnesund chosen
    Minnesund is a small village in Eidsvoll Municipality in Norway, situated at the southern end of Lake Mjøsa and known as a key transport junction.
  • B. Sundet
    Sundet is the main town and local hub of Eidsvoll municipality in Norway, serving as its commercial and service center.
  • C. Follebu
    Follebu is a village in Innlandet county, Norway, known for its rural setting and traditional Norwegian countryside character within Gausdal municipality.
  • D. Namdalseid
    Namdalseid is a former rural municipality in Trøndelag county, Norway, known for its forests, agriculture, and coastal landscape along the Namsenfjorden.
  • E. Sennevika
    Sennevika is a small settlement located on the island of Senja in northern Norway, known for its coastal Arctic landscape.
  • 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0027925788190b955fdc6626adf7d completed April 15, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7e47b20819084145008474f47b7 completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:04 a.m.