Triple

T35538535
Position Surface form Disambiguated ID Type / Status
Subject Cercedilla E1026997 entity
Predicate governingBody P46 FINISHED
Object Ayuntamiento de Cercedilla
Ayuntamiento de Cercedilla is the municipal council and local government authority responsible for administering the town of Cercedilla in Spain.
E2143341 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: Ayuntamiento de Cercedilla | Statement: [Cercedilla, governingBody, Ayuntamiento de Cercedilla]
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: Ayuntamiento de Cercedilla
Triple: [Cercedilla, governingBody, Ayuntamiento de Cercedilla]
Generated description
Ayuntamiento de Cercedilla is the municipal council and local government authority responsible for administering the town of Cercedilla in Spain.

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_69f76dff7e508190b28ceeee770dce23 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7980391bc8190b7465c3324e3bcc2 completed May 3, 2026, 6:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a384a4cfcf4819084b4ce6c8b55d16e completed June 21, 2026, 8:32 p.m.
NEDg Description generation batch_6a384ad82c988190af80953f8489337d completed June 21, 2026, 8:34 p.m.
NED2 Entity disambiguation (via description) batch_6a384b40725c819094bcd2704b986724 completed June 21, 2026, 8:36 p.m.
Created at: May 3, 2026, 4:04 p.m.