Triple

T28993425
Position Surface form Disambiguated ID Type / Status
Subject Dorrego station E736089 entity
Predicate namedAfter P63 FINISHED
Object Avenida Dorrego
Avenida Dorrego is a major avenue in Buenos Aires, Argentina, known for running through several central neighborhoods and serving as an important urban thoroughfare.
E2033541 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: Avenida Dorrego | Statement: [Dorrego station, namedAfter, Avenida Dorrego]
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: Avenida Dorrego
Triple: [Dorrego station, namedAfter, Avenida Dorrego]
Generated description
Avenida Dorrego is a major avenue in Buenos Aires, Argentina, known for running through several central neighborhoods and serving as an important urban thoroughfare.

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_69f077eacd0481908ef0bafd74491cd0 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f65f7f067081909057e9c6e1fd0bdd completed May 2, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a34e4e3ff988190b4c6a2d4cd0b3f14 completed June 19, 2026, 6:42 a.m.
NEDg Description generation batch_6a34e5b49a648190aca8b4ea64bb77da completed June 19, 2026, 6:46 a.m.
NED2 Entity disambiguation (via description) batch_6a34e66fc7fc81908758e4f67ce150b4 completed June 19, 2026, 6:49 a.m.
Created at: April 28, 2026, 9:28 a.m.