Triple

T28603292
Position Surface form Disambiguated ID Type / Status
Subject Porta Pia E723970 entity
Predicate hasNearbySquare P7888 FINISHED
Object Piazza di Porta Pia
Piazza di Porta Pia is a historic square in Rome located near the 16th-century Porta Pia gate, known for its urban setting and proximity to important governmental buildings.
E1879640 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 di Porta Pia | Statement: [Porta Pia, hasNearbySquare, Piazza di Porta Pia]
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 di Porta Pia
Triple: [Porta Pia, hasNearbySquare, Piazza di Porta Pia]
Generated description
Piazza di Porta Pia is a historic square in Rome located near the 16th-century Porta Pia gate, known for its urban setting and proximity to important governmental buildings.

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_69f01d80b1908190980594837604b8c7 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f65217aee0819091c32d56b63de24d completed May 2, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a267e8d6ed48190bd48b474c1ad2ec4 completed June 8, 2026, 8:34 a.m.
NEDg Description generation batch_6a2682d3fa3c81909e0736cb74338f7e completed June 8, 2026, 8:52 a.m.
NED2 Entity disambiguation (via description) batch_6a26883b773081908ee6cad8a66f0251 completed June 8, 2026, 9:15 a.m.
Created at: April 28, 2026, 4:25 a.m.