Triple

T35651703
Position Surface form Disambiguated ID Type / Status
Subject Cono Norte of Lima E1030167 entity
Predicate hasTransportAxis P11026 FINISHED
Object Universitaria Avenue
Universitaria Avenue is a major thoroughfare and public transport corridor in Lima, Peru, that connects several districts across the city’s northern area.
E2180070 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: Universitaria Avenue | Statement: [Cono Norte of Lima, hasTransportAxis, Universitaria Avenue]
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: Universitaria Avenue
Triple: [Cono Norte of Lima, hasTransportAxis, Universitaria Avenue]
Generated description
Universitaria Avenue is a major thoroughfare and public transport corridor in Lima, Peru, that connects several districts across the city’s northern area.

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_69f76e0938088190a8f199631e97dec3 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f751e9c81909b8d9b6a7d6604be completed May 3, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39a3022bf48190b54a903c2437cffe completed June 22, 2026, 9:02 p.m.
NEDg Description generation batch_6a39a64ebcac8190b7656fc9263d7e36 completed June 22, 2026, 9:17 p.m.
NED2 Entity disambiguation (via description) batch_6a39a6dfc1c881909a4985813be8fcdd completed June 22, 2026, 9:19 p.m.
Created at: May 3, 2026, 4:05 p.m.