Triple

T38572942
Position Surface form Disambiguated ID Type / Status
Subject Canal Imperial de Aragón E929324 entity
Predicate hasBridge P386 FINISHED
Object Puente de la Unión (Zaragoza)
Puente de la Unión is a bridge in Zaragoza, Spain, that spans the Canal Imperial de Aragón and serves as a key local crossing point within the city’s transport network.
E2278960 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: Puente de la Unión (Zaragoza) | Statement: [Canal Imperial de Aragón, hasBridge, Puente de la Unión (Zaragoza)]
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: Puente de la Unión (Zaragoza)
Triple: [Canal Imperial de Aragón, hasBridge, Puente de la Unión (Zaragoza)]
Generated description
Puente de la Unión is a bridge in Zaragoza, Spain, that spans the Canal Imperial de Aragón and serves as a key local crossing point within the city’s transport network.

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_69f76ebd2248819083978362d81fa35e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd91eb5708190898c62af8c8201c1 completed May 7, 2026, 6:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41f434bb3081909694ba026a81b463 completed June 29, 2026, 4:27 a.m.
NEDg Description generation batch_6a41f4fbde8c819096617301e3ece13c completed June 29, 2026, 4:30 a.m.
NED2 Entity disambiguation (via description) batch_6a41f8d699bc8190a33eea34eff1e4d8 completed June 29, 2026, 4:47 a.m.
Created at: May 3, 2026, 4:32 p.m.