Triple

T35557613
Position Surface form Disambiguated ID Type / Status
Subject Engesland E1027541 entity
Predicate hasBuilding P105 FINISHED
Object Engesland Church
Engesland Church is a small parish church serving the local community of Engesland in Norway, known for its traditional rural architecture and role as a local religious and cultural center.
E2147179 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: Engesland Church | Statement: [Engesland, hasBuilding, Engesland 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: Engesland Church
Triple: [Engesland, hasBuilding, Engesland Church]
Generated description
Engesland Church is a small parish church serving the local community of Engesland in Norway, known for its traditional rural architecture and role as a local religious and cultural center.

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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79840c2b4819099b8e456f718021c completed May 3, 2026, 6:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a385bcc897481909b6324ad06b46f50 completed June 21, 2026, 9:46 p.m.
NEDg Description generation batch_6a385d4a1b9c81908f8eaca4b6fb952e completed June 21, 2026, 9:53 p.m.
NED2 Entity disambiguation (via description) batch_6a385dd6f1808190ab7f9530743cf1d6 completed June 21, 2026, 9:55 p.m.
Created at: May 3, 2026, 4:04 p.m.