Triple

T30132646
Position Surface form Disambiguated ID Type / Status
Subject Valmadrera E765887 entity
Predicate hasOfficialName P66 FINISHED
Object Comune di Valmadrera
Comune di Valmadrera is an Italian municipality located in the Lombardy region, in the Province of Lecco, near the southeastern branch of Lake Como.
E1900677 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: Comune di Valmadrera | Statement: [Valmadrera, hasOfficialName, Comune di Valmadrera]
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: Comune di Valmadrera
Triple: [Valmadrera, hasOfficialName, Comune di Valmadrera]
Generated description
Comune di Valmadrera is an Italian municipality located in the Lombardy region, in the Province of Lecco, near the southeastern branch of Lake Como.

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_69f22477d1a081908df2b7e6ed16859d completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67e491014819080bd41f2195f92c0 completed May 2, 2026, 10:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a274cb28ef0819091e0e7730db8ac07 completed June 8, 2026, 11:13 p.m.
NEDg Description generation batch_6a274d28646081909e25c4cb14a4cbf0 completed June 8, 2026, 11:15 p.m.
NED2 Entity disambiguation (via description) batch_6a274e0019dc81908c8911898b2336a9 completed June 8, 2026, 11:19 p.m.
Created at: April 29, 2026, 7:15 p.m.