Triple

T14028545
Position Surface form Disambiguated ID Type / Status
Subject Hadeland E337526 entity
Predicate hasHistoricSite P1098 FINISHED
Object Nes church ruin E862698 NE FINISHED

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: Nes church ruin | Statement: [Hadeland, hasHistoricSite, Nes church ruin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nes church ruin
Context triple: [Hadeland, hasHistoricSite, Nes church ruin]
  • A. Nes Church chosen
    Nes Church is a historic parish church in the village of Nes in Akershus, Norway, serving as a local center of Lutheran worship and community life.
  • B. Kuortane Church
    Kuortane Church is a historic wooden Lutheran church in the municipality of Kuortane in South Ostrobothnia, Finland.
  • C. Bykle Church
    Bykle Church is a parish church in the village of Bykle in Agder county, Norway, serving as a local center of Lutheran worship and community life.
  • D. Dirdal Church
    Dirdal Church is a parish church in the village of Dirdal in Gjesdal Municipality, Rogaland county, Norway, serving the local Lutheran congregation.
  • E. Ballangen Church
    Ballangen Church is a parish church of the Church of Norway located in the village of Ballangen in Nordland county.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2fa830ac81908cb7df7c9e81e42a completed April 14, 2026, 12:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc335a474819084c310b10e0ded9a completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:20 p.m.