Triple

T18240635
Position Surface form Disambiguated ID Type / Status
Subject Vestre Slidre E436798 entity
Predicate hasHistoricSite P1098 FINISHED
Object Rogne 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: Rogne Church | Statement: [Vestre Slidre, hasHistoricSite, Rogne Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rogne Church
Context triple: [Vestre Slidre, hasHistoricSite, Rogne Church]
  • A. Rogne Church chosen
    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.
  • B. Noresund Church
    Noresund Church is a parish church serving the local community in the village of Noresund in Krødsherad, Norway.
  • C. Rødenes Church
    Rødenes Church is a historic medieval parish church in Rødenes, Norway, noted for its traditional stone architecture and cultural significance.
  • D. Udenes Church
    Udenes Church is a historic parish church in Nes, Akershus, Norway, known for serving as a local center of Lutheran worship and community life.
  • E. Valbo Church
    Valbo Church is a historic parish church in Valbo, Sweden, serving as a central place of worship and community gathering for the local Lutheran congregation.
  • 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_69d8b91104e08190a8241f7d260a5162 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f7e287548190b666a990e5b168b0 completed April 19, 2026, 3:42 p.m.
Created at: April 10, 2026, 10:33 a.m.