Triple

T17370908
Position Surface form Disambiguated ID Type / Status
Subject Hole E422310 entity
Predicate hasHistoricalSite P1098 FINISHED
Object Bønsnes 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: Bønsnes church | Statement: [Hole, hasHistoricalSite, Bønsnes church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bønsnes church
Context triple: [Hole, hasHistoricalSite, Bønsnes church]
  • A. Bønsnes Church chosen
    Bønsnes Church is a historic parish church in Hole, Norway, known for its medieval origins and traditional Norwegian architectural style.
  • B. 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.
  • C. Billefjord Church
    Billefjord Church is a small parish church serving the local community in the village of Billefjord in Porsanger, Norway.
  • D. Rygge Church
    Rygge Church is a historic medieval stone church located in Rygge, Norway, known for its Romanesque architecture and cultural significance.
  • E. Brattvåg Church
    Brattvåg Church is a parish church of the Church of Norway located in the village of Brattvåg in Haram Municipality, Møre og Romsdal 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a68ff448190b505861e56df5b6d completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:44 a.m.