Triple

T23082711
Position Surface form Disambiguated ID Type / Status
Subject Støren E575518 entity
Predicate hasChurch P15000 FINISHED
Object Støren 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: Støren Church | Statement: [Støren, hasChurch, Støren Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Støren Church
Context triple: [Støren, hasChurch, Støren Church]
  • A. Støren Church chosen
    Støren Church is a historic parish church of the Church of Norway located in the village of Støren in Trøndelag county.
  • B. Stordal Church
    Stordal Church is a historic parish church in Norway, known for serving the local community of Stordal with traditional Norwegian ecclesiastical architecture.
  • C. Rygge Church
    Rygge Church is a historic medieval stone church located in Rygge, Norway, known for its Romanesque architecture and cultural significance.
  • D. Øyer Church
    Øyer Church is a historic parish church in the village of Øyer in Innlandet county, Norway, serving as a local center of Lutheran worship and community life.
  • E. Kvernes Church
    Kvernes Church is a historic wooden parish church in Kvernes on Averøya in Møre og Romsdal, Norway, known for its preserved 17th-century architecture and interior.
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da239e48190ad041261c6b510a0 completed April 29, 2026, 4:48 a.m.
Created at: April 17, 2026, 3:56 p.m.