Triple

T18112937
Position Surface form Disambiguated ID Type / Status
Subject Lesja E433526 entity
Predicate contains P35 FINISHED
Object Lesja 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: Lesja Church | Statement: [Lesja, contains, Lesja Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lesja Church
Context triple: [Lesja, contains, Lesja Church]
  • A. Lesja Church chosen
    Lesja Church is a historic parish church in Norway, known for its traditional wooden architecture and role as a central place of worship in the rural community of Lesja.
  • B. 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.
  • C. 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.
  • D. Salangen Church
    Salangen Church is a parish church of the Church of Norway located in the village of Sjøvegan in Salangen Municipality, Troms og Finnmark county.
  • E. Hausken Church
    Hausken Church is a parish church of the Church of Norway located on the island municipality of Rennesøy in Rogaland county.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd3fd9c81909bfe95927f7553e3 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:28 a.m.