Triple

T34181569
Position Surface form Disambiguated ID Type / Status
Subject Rakkestad municipality E876832 entity
Predicate hasChurch P15000 FINISHED
Object Degernes Church
Degernes Church is a historic parish church in the village of Degernes in Rakkestad, Norway, serving as a local center of Lutheran worship and community life.
E2104078 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: Degernes Church | Statement: [Rakkestad municipality, hasChurch, Degernes Church]
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: Degernes Church
Triple: [Rakkestad municipality, hasChurch, Degernes Church]
Generated description
Degernes Church is a historic parish church in the village of Degernes in Rakkestad, Norway, serving as a local center of Lutheran worship and community life.

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_69f349ae640c8190b9cd220b5368d8b6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7100548bc8190b641d53a39abee5e completed May 3, 2026, 9:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3740ee9c688190bc1f936bf4410d79 completed June 21, 2026, 1:39 a.m.
NEDg Description generation batch_6a3741e4792081908c15fe94588e4f67 completed June 21, 2026, 1:44 a.m.
NED2 Entity disambiguation (via description) batch_6a3743223b3881909db5005278415166 completed June 21, 2026, 1:49 a.m.
Created at: May 1, 2026, 1:54 a.m.