Triple

T17742083
Position Surface form Disambiguated ID Type / Status
Subject Untertorbrücke E442884 entity
Predicate near P350 FINISHED
Object Nydegg 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: Nydegg Church | Statement: [Untertorbrücke, near, Nydegg Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nydegg Church
Context triple: [Untertorbrücke, near, Nydegg Church]
  • A. Nydegg Church chosen
    Nydegg Church is a historic Protestant church in Bern’s Old City, notable for its medieval origins and prominent location overlooking the Aare River.
  • B. Veggli Church
    Veggli Church is a historic parish church in the village of Veggli in Rollag Municipality, Norway, serving as a local center of Lutheran worship and community life.
  • C. Talgje Church
    Talgje Church is a historic parish church located on the island of Talgje in Rogaland county, Norway.
  • 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. Bardu Church
    Bardu Church is a historic parish church in Bardu Municipality in Troms og Finnmark county, Norway, known for its distinctive wooden architecture and role as a central place of worship for the local community.
  • 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e47acd780c8190b1308ef0aca00f5c completed April 19, 2026, 6:48 a.m.
Created at: April 10, 2026, 10:09 a.m.