Triple

T18258636
Position Surface form Disambiguated ID Type / Status
Subject Tretten parish E437285 entity
Predicate parishSeat P383 FINISHED
Object Tretten 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: Tretten Church | Statement: [Tretten parish, parishSeat, Tretten Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tretten Church
Context triple: [Tretten parish, parishSeat, Tretten Church]
  • A. Tretten Church chosen
    Tretten Church is a historic parish church located in the village of Tretten in Øyer Municipality, Innlandet county, Norway.
  • B. Bamble Church
    Bamble Church is a historic parish church in Bamble, Norway, known for its traditional architecture and role as a local religious and cultural landmark.
  • C. Bygland Church
    Bygland Church is a historic parish church in the village of Bygland in Agder county, Norway, serving as a local center of Lutheran worship and community life.
  • D. Sylling Church
    Sylling Church is a historic parish church serving the village of Sylling in Lier Municipality, Norway.
  • E. Vinstra Church
    Vinstra Church is a parish church in Norway serving the local community of Vinstra with regular worship and religious ceremonies.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4fd8879e88190893f8da7c3529496 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 10:34 a.m.