Triple

T31958724
Position Surface form Disambiguated ID Type / Status
Subject Viali di Circonvallazione E815975 entity
Predicate hasPart P35 FINISHED
Object Viale Lorenzo Magnifico
Viale Lorenzo Magnifico is a major urban thoroughfare in Rome that forms part of the city’s Viali di Circonvallazione ring road system.
E2022421 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: Viale Lorenzo Magnifico | Statement: [Viali di Circonvallazione, hasPart, Viale Lorenzo Magnifico]
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: Viale Lorenzo Magnifico
Triple: [Viali di Circonvallazione, hasPart, Viale Lorenzo Magnifico]
Generated description
Viale Lorenzo Magnifico is a major urban thoroughfare in Rome that forms part of the city’s Viali di Circonvallazione ring road system.

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_6a34b1435b748190896af3d2104e629c completed June 19, 2026, 3:02 a.m.
NEDg Description generation batch_6a34b20dec888190920a1472083382c0 completed June 19, 2026, 3:05 a.m.
NED2 Entity disambiguation (via description) batch_6a34b2b0f36c8190ab30af3d30024b97 completed June 19, 2026, 3:08 a.m.
Created at: May 1, 2026, 12:08 a.m.