Triple

T19198308
Position Surface form Disambiguated ID Type / Status
Subject Lensvik E470029 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Lensvik 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: Lensvik Church | Statement: [Lensvik, hasReligiousBuilding, Lensvik Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lensvik Church
Context triple: [Lensvik, hasReligiousBuilding, Lensvik Church]
  • A. Lensvik Church chosen
    Lensvik Church is a parish church of the Church of Norway located in the village of Lensvik in Agdenes, Trøndelag.
  • B. Bleikvassli Church
    Bleikvassli Church is a parish church of the Church of Norway located in the village of Bleikvasslia in Hemnes Municipality, Nordland county.
  • C. Ulvik Church
    Ulvik Church is a historic parish church in the village of Ulvik in western Norway, known for its traditional wooden architecture and scenic fjordside setting.
  • D. 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.
  • E. Harestua Church
    Harestua Church is a parish church serving the local community in the village of Harestua in Lunner, Norway.
  • 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f8a8daac8190b3558a1388596fb0 completed April 20, 2026, 9:58 a.m.
Created at: April 10, 2026, 12:07 p.m.