Triple

T27383097
Position Surface form Disambiguated ID Type / Status
Subject Zeist E691289 entity
Predicate governedBy P46 FINISHED
Object municipal council of Zeist
The municipal council of Zeist is the elected local governing body responsible for setting policy and overseeing administration in the Dutch municipality of Zeist.
E1770276 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 Zeist | Statement: [Zeist, governedBy, municipal council of Zeist]
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 Zeist
Triple: [Zeist, governedBy, municipal council of Zeist]
Generated description
The municipal council of Zeist is the elected local governing body responsible for setting policy and overseeing administration in the Dutch municipality of Zeist.

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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62c88e488819084542a60d9e6bf82 completed May 2, 2026, 4:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12a7ede8688190aaad6460b5bad00f completed May 24, 2026, 7:25 a.m.
NEDg Description generation batch_6a12a87492b48190be0461fafe4d081d completed May 24, 2026, 7:27 a.m.
NED2 Entity disambiguation (via description) batch_6a12a926a67c819083713f0245b3e299 completed May 24, 2026, 7:30 a.m.
Created at: April 27, 2026, 12:23 p.m.