Triple

T27161799
Position Surface form Disambiguated ID Type / Status
Subject Pyhtää E682678 entity
Predicate governingBody P46 FINISHED
Object Pyhtää municipal council
Pyhtää municipal council is the elected decision-making body responsible for local governance, budgeting, and municipal policies in the Finnish municipality of Pyhtää.
E1761095 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: Pyhtää municipal council | Statement: [Pyhtää, governingBody, Pyhtää municipal council]
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: Pyhtää municipal council
Triple: [Pyhtää, governingBody, Pyhtää municipal council]
Generated description
Pyhtää municipal council is the elected decision-making body responsible for local governance, budgeting, and municipal policies in the Finnish municipality of Pyhtää.

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_69eefacf6e788190a75a64399d9e3109 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6250b1b248190950a94cd6fe1d479 completed May 2, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1253809ba88190a3f3755882899b80 completed May 24, 2026, 1:25 a.m.
NEDg Description generation batch_6a12546f814881908c806a1805b7473d completed May 24, 2026, 1:29 a.m.
NED2 Entity disambiguation (via description) batch_6a12552837d88190a12496ca49423f0f completed May 24, 2026, 1:32 a.m.
Created at: April 27, 2026, 9:19 a.m.