Triple

T28702816
Position Surface form Disambiguated ID Type / Status
Subject Comune di Reggio nell’Emilia E729598 entity
Predicate hasMunicipalSeat P1474 FINISHED
Object Reggio Emilia city hall
Reggio Emilia city hall is the main administrative building and seat of local government for the Italian city of Reggio Emilia.
E1831239 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: Reggio Emilia city hall | Statement: [Comune di Reggio nell’Emilia, hasMunicipalSeat, Reggio Emilia city hall]
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: Reggio Emilia city hall
Triple: [Comune di Reggio nell’Emilia, hasMunicipalSeat, Reggio Emilia city hall]
Generated description
Reggio Emilia city hall is the main administrative building and seat of local government for the Italian city of Reggio Emilia.

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_69f043e6e9688190b6bdd6e5665498ff completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f656b603f881909486b77c99aa6104 completed May 2, 2026, 7:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf4e6b908190a6da3c750f82f0de completed June 1, 2026, 12:16 a.m.
NEDg Description generation batch_6a1cd03986848190a322d5273d0164d0 completed June 1, 2026, 12:20 a.m.
NED2 Entity disambiguation (via description) batch_6a24946ccd908190ae144fbc7010aca9 completed June 6, 2026, 9:43 p.m.
Created at: April 28, 2026, 5:43 a.m.