Triple

T21775267
Position Surface form Disambiguated ID Type / Status
Subject Hovin Church E537554 entity
Predicate serves P98 FINISHED
Object Hovin parish community 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: Hovin parish community | Statement: [Hovin Church, serves, Hovin parish community]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hovin parish community
Context triple: [Hovin Church, serves, Hovin parish community]
  • A. Hovin parish chosen
    Hovin parish is a Church of Norway parish centered around Hovin Church, serving the local Lutheran congregation in the Hovin area of Norway.
  • B. Sunnylven parish
    Sunnylven parish is a local Church of Norway parish serving the community within Stranda Municipality in Møre og Romsdal county.
  • C. 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.
  • D. Haug parish
    Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
  • E. Hokksund parish
    Hokksund parish is a Church of Norway parish serving the town and surrounding area of Hokksund in Øvre Eiker, Buskerud, Norway.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04627bd488190bbc1fde8db417b55 completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:51 p.m.