Triple

T15532040
Position Surface form Disambiguated ID Type / Status
Subject Giske E370242 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Vigra Church E1153639 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: Vigra Church | Statement: [Giske, hasReligiousBuilding, Vigra Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vigra Church
Context triple: [Giske, hasReligiousBuilding, Vigra Church]
  • A. Vigra Church chosen
    Vigra Church is a parish church of the Church of Norway located on the island of Vigra in Giske Municipality, Møre og Romsdal county.
  • B. Fogn Church
    Fogn Church is a parish church serving the local community on the island of Fogn in Finnøy, Norway.
  • C. Rogne Church
    Rogne Church is a historic parish church in the village of Rogne in Øystre Slidre, Innlandet county, Norway, known for serving the local Lutheran congregation.
  • D. Ikornnes Church
    Ikornnes Church is a parish church of the Church of Norway located in the village of Ikornnes in Sykkylven Municipality, Møre og Romsdal county.
  • 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 (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_69d85cc521a08190921fb50319dddc34 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e0414877d88190804ee76566004e13 completed April 16, 2026, 1:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff45549e4881908ab0769e49ba5dc4 completed May 9, 2026, 2:31 p.m.
Created at: April 10, 2026, 4:06 a.m.