Triple

T19560651
Position Surface form Disambiguated ID Type / Status
Subject Røyken E489438 entity
Predicate hasParishChurch P1191 FINISHED
Object Røyken Church
Røyken Church is a historic parish church in Røyken, Norway, known for its medieval origins and traditional stone architecture.
 E1414137 NE FINISHED

How this triple was built (4 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: Røyken Church | Statement: [Røyken, hasParishChurch, Røyken Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Røyken Church
Context triple: [Røyken, hasParishChurch, Røyken Church]
  • A. Oppstad Church
    Oppstad Church is a parish church serving the local community in Sør-Odal municipality in Innlandet county, Norway.
  • B. Rygge Church
    Rygge Church is a historic medieval stone church located in Rygge, Norway, known for its Romanesque architecture and cultural significance.
  • C. Kongsberg Church
    Kongsberg Church is a historic 18th-century Baroque-style church in Kongsberg, Norway, noted for its richly decorated interior and significant organ.
  • D. Gjerdrum Church
    Gjerdrum Church is a historic parish church in Gjerdrum, Norway, serving as a local center for Lutheran worship and community life.
  • E. Brøstad Church
    Brøstad Church is a parish church of the Church of Norway located in the village of Brøstadbotn in northern Norway.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Røyken Church
Triple: [Røyken, hasParishChurch, Røyken Church]
Generated description
Røyken Church is a historic parish church in Røyken, Norway, known for its medieval origins and traditional stone architecture.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Røyken Church
Target entity description: Røyken Church is a historic parish church in Røyken, Norway, known for its medieval origins and traditional stone architecture.
  • A. Oppstad Church
    Oppstad Church is a parish church serving the local community in Sør-Odal municipality in Innlandet county, Norway.
  • B. Rygge Church
    Rygge Church is a historic medieval stone church located in Rygge, Norway, known for its Romanesque architecture and cultural significance.
  • C. Kongsberg Church
    Kongsberg Church is a historic 18th-century Baroque-style church in Kongsberg, Norway, noted for its richly decorated interior and significant organ.
  • D. Gjerdrum Church
    Gjerdrum Church is a historic parish church in Gjerdrum, Norway, serving as a local center for Lutheran worship and community life.
  • E. Brøstad Church
    Brøstad Church is a parish church of the Church of Norway located in the village of Brøstadbotn in northern Norway.
  • F. None of above. chosen

Provenance (5 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63f7442e08190ad030151ec0a97d4 completed April 20, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0834545e1c81908bf32a30663202ae completed May 16, 2026, 9:09 a.m.
NEDg Description generation batch_6a08353703b88190b8eef21650bad944 completed May 16, 2026, 9:13 a.m.
NED2 Entity disambiguation (via description) batch_6a0835c4c9f48190b4d568814729a7ca completed May 16, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:42 p.m.