Triple

T18326620
Position Surface form Disambiguated ID Type / Status
Subject Eidsberg E439024 entity
Predicate hasHeritageSite P923 FINISHED
Object Eidsberg 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: Eidsberg Church | Statement: [Eidsberg, hasHeritageSite, Eidsberg Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eidsberg Church
Context triple: [Eidsberg, hasHeritageSite, Eidsberg Church]
  • A. Eidsberg Church chosen
    Eidsberg Church is a historic parish church in Eidsberg, Norway, known for its medieval origins and traditional Norwegian architectural style.
  • B. Borge Church
    Borge Church is a parish church in Norway serving the local Borge community as a center for Lutheran worship and congregational life.
  • C. Lunner Church
    Lunner Church is a historic parish church in Lunner, Norway, known for its medieval origins and traditional Norwegian architectural style.
  • 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. Jessheim Church
    Jessheim Church is a parish church in the town of Jessheim in Ullensaker, Norway, serving as a local center for Lutheran worship and community activities.
  • 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aab3e7c81909b1c0a688707dfd6 completed April 19, 2026, 5:02 p.m.
Created at: April 10, 2026, 10:36 a.m.