Triple

T23096843
Position Surface form Disambiguated ID Type / Status
Subject Sandvollan Church E575913 entity
Predicate parish P2739 FINISHED
Object Sandvollan parish 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: Sandvollan parish | Statement: [Sandvollan Church, parish, Sandvollan parish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandvollan parish
Context triple: [Sandvollan Church, parish, Sandvollan parish]
  • A. Sandvollan parish chosen
    Sandvollan parish is a local Church of Norway parish serving the Sandvollan area within the municipality of Inderøy in Trøndelag county.
  • B. Vanylven parish
    Vanylven parish is a Church of Norway parish serving the local Lutheran congregation in the Vanylven area of Møre og Romsdal county, Norway.
  • C. Svene parish
    Svene parish is a local ecclesiastical and historical administrative area within the municipality of Flesberg in Norway.
  • D. Volda parish
    Volda parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Volda in western Norway.
  • E. Avaldsnes parish
    Avaldsnes parish is a Church of Norway parish centered around the historic Avaldsnes Church on the island of Karmøy in Rogaland county.
  • 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_69e245c060b48190a9bd61a47a16db17 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18de522e48190a37e6c2fda2de465 completed April 29, 2026, 4:49 a.m.
Created at: April 17, 2026, 3:57 p.m.