Triple

T33491445
Position Surface form Disambiguated ID Type / Status
Subject Mexican War Streets E857748 entity
Predicate hasStreet P959 FINISHED
Object Perrysville Avenue
Perrysville Avenue is a notable street in Pittsburgh, Pennsylvania, running through and beyond the historic Mexican War Streets neighborhood on the city’s North Side.
E2296096 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: Perrysville Avenue | Statement: [Mexican War Streets, hasStreet, Perrysville 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: Perrysville Avenue
Triple: [Mexican War Streets, hasStreet, Perrysville Avenue]
Generated description
Perrysville Avenue is a notable street in Pittsburgh, Pennsylvania, running through and beyond the historic Mexican War Streets neighborhood on the city’s North Side.

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_69f3497547608190a1a0f2365fb713ee completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e5670c048190ae7e5435e9a8e97f completed May 3, 2026, 6:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a8232ff92248190aa78efddfdc36dd5 completed Aug. 16, 2026, 10 p.m.
NEDg Description generation batch_6a8233d5a0d88190adf09d4299359728 completed Aug. 16, 2026, 10:04 p.m.
NED2 Entity disambiguation (via description) batch_6a8234285f6c8190b6bd4abe777b15db completed Aug. 16, 2026, 10:05 p.m.
Created at: May 1, 2026, 1:38 a.m.