Triple

T17371007
Position Surface form Disambiguated ID Type / Status
Subject Krødsherad E422312 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Krødsherad 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: Krødsherad Church | Statement: [Krødsherad, hasReligiousBuilding, Krødsherad Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krødsherad Church
Context triple: [Krødsherad, hasReligiousBuilding, Krødsherad Church]
  • A. Krødsherad Church chosen
    Krødsherad Church is a parish church serving the local community in Krødsherad, Norway, and is part of the Church of Norway.
  • B. Rødenes Church
    Rødenes Church is a historic medieval parish church in Rødenes, Norway, noted for its traditional stone architecture and cultural significance.
  • C. Finnås Church
    Finnås Church is a historic parish church in Finnås, Norway, serving as a local center of Lutheran worship and community life.
  • D. Rygge Church
    Rygge Church is a historic medieval stone church located in Rygge, Norway, known for its Romanesque architecture and cultural significance.
  • E. Romedal Church
    Romedal Church is a historic parish church in Innlandet county, Norway, known for its medieval origins and traditional Norwegian architectural style.
  • 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.