Triple

T37896673
Position Surface form Disambiguated ID Type / Status
Subject Wohlen E945299 entity
Predicate governingBody P46 FINISHED
Object municipal council of Wohlen
The municipal council of Wohlen is the local executive authority responsible for administering and managing the municipality of Wohlen in Switzerland.
E2247563 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: municipal council of Wohlen | Statement: [Wohlen, governingBody, municipal council of Wohlen]
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: municipal council of Wohlen
Triple: [Wohlen, governingBody, municipal council of Wohlen]
Generated description
The municipal council of Wohlen is the local executive authority responsible for administering and managing the municipality of Wohlen in Switzerland.

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_69f76ef0e8708190987c7254ed8c7abe completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbd3bb1f88190a648fadd2175dbf5 completed May 6, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41043bd3c88190a30cfa996f24c61c completed June 28, 2026, 11:23 a.m.
NEDg Description generation batch_6a4104e34d508190aa5b6606bd812409 completed June 28, 2026, 11:26 a.m.
NED2 Entity disambiguation (via description) batch_6a4106705f7881908428bc38ccfb838c completed June 28, 2026, 11:33 a.m.
Created at: May 3, 2026, 4:19 p.m.