Triple

T36332776
Position Surface form Disambiguated ID Type / Status
Subject Wedel E894696 entity
Predicate governingBody P46 FINISHED
Object Wedel town council
The Wedel town council is the elected municipal governing body responsible for local legislation, administration oversight, and policy decisions in the town of Wedel, Germany.
E2179202 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: Wedel town council | Statement: [Wedel, governingBody, Wedel town 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: Wedel town council
Triple: [Wedel, governingBody, Wedel town council]
Generated description
The Wedel town council is the elected municipal governing body responsible for local legislation, administration oversight, and policy decisions in the town of Wedel, Germany.

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_69f76e4dcf088190a6c3216c209cab52 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba70ac6081909a8645280f42bba9 completed May 3, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a397d9b09bc8190a76ee1f70c473b5b completed June 22, 2026, 6:23 p.m.
NEDg Description generation batch_6a398d05ec64819094a1ddb66ad32128 completed June 22, 2026, 7:29 p.m.
NED2 Entity disambiguation (via description) batch_6a398e1a986881908c6727fd6a03cffd completed June 22, 2026, 7:33 p.m.
Created at: May 3, 2026, 4:09 p.m.