Triple

T31563167
Position Surface form Disambiguated ID Type / Status
Subject Sonkajärvi E805325 entity
Predicate hasAdministrativeCentre P1474 FINISHED
Object Sonkajärvi church village
Sonkajärvi church village is the main settlement and local hub of the municipality of Sonkajärvi in Northern Savonia, Finland.
E1968353 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: Sonkajärvi church village | Statement: [Sonkajärvi, hasAdministrativeCentre, Sonkajärvi church village]
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: Sonkajärvi church village
Triple: [Sonkajärvi, hasAdministrativeCentre, Sonkajärvi church village]
Generated description
Sonkajärvi church village is the main settlement and local hub of the municipality of Sonkajärvi in Northern Savonia, Finland.

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_69f348d2ee94819091918d1789398c29 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a7ca9edc8190a222f6382a196472 completed May 3, 2026, 1:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b2d979c34819098c464ee67f8c22c completed June 11, 2026, 9:50 p.m.
NEDg Description generation batch_6a2b4ad8c5488190b07d616fc101cbad completed June 11, 2026, 11:55 p.m.
NED2 Entity disambiguation (via description) batch_6a2b4e85f540819096d5a2540e07f702 completed June 12, 2026, 12:10 a.m.
Created at: April 30, 2026, 10:16 p.m.