Triple

T21775309
Position Surface form Disambiguated ID Type / Status
Subject Nes (Viken) E537555 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Fenstad Church 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: Fenstad Church | Statement: [Nes (Viken), hasReligiousBuilding, Fenstad Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fenstad Church
Context triple: [Nes (Viken), hasReligiousBuilding, Fenstad Church]
  • A. Fenstad Church chosen
    Fenstad Church is a parish church serving the village of Fenstad in Nes municipality in Akershus, Norway, and is part of the Church of Norway.
  • B. Vålerenga Church
    Vålerenga Church is a historic parish church in the Vålerenga neighborhood of Oslo, Norway, known for its distinctive architecture and role as a local landmark.
  • C. Fjell Church
    Fjell Church is a parish church in Vestland county, Norway, serving the local community of the former Fjell municipality on the island of Sotra.
  • D. Oppstad Church
    Oppstad Church is a parish church serving the local community in Sør-Odal municipality in Innlandet county, Norway.
  • E. Sakshaug Church
    Sakshaug Church is a historic parish church in the village of Sakshaug in Inderøy, Trøndelag, Norway, known for its medieval origins and stone architecture.
  • 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.