Triple

T31958737
Position Surface form Disambiguated ID Type / Status
Subject Viali di Circonvallazione E815975 entity
Predicate hasPart P35 FINISHED
Object Piazza Beccaria
Piazza Beccaria is a major square in Florence, Italy, known as a key traffic junction on the city’s eastern ring road and for its 19th-century urban layout.
E2000626 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: Piazza Beccaria | Statement: [Viali di Circonvallazione, hasPart, Piazza Beccaria]
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: Piazza Beccaria
Triple: [Viali di Circonvallazione, hasPart, Piazza Beccaria]
Generated description
Piazza Beccaria is a major square in Florence, Italy, known as a key traffic junction on the city’s eastern ring road and for its 19th-century urban layout.

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_69f348f4ec708190abbb2a7c3ed58844 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2b0d044819085a28c5114423542 completed May 3, 2026, 2:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f46b5f7988190ab8d025b24852e74 completed June 15, 2026, 12:26 a.m.
NEDg Description generation batch_6a2f47d66a34819082bc75aaf3f2b197 completed June 15, 2026, 12:31 a.m.
NED2 Entity disambiguation (via description) batch_6a301ae519348190a8563be3d2c124d0 completed June 15, 2026, 3:31 p.m.
Created at: May 1, 2026, 12:08 a.m.