Triple

T33389308
Position Surface form Disambiguated ID Type / Status
Subject Allegheny West (Pittsburgh) E855000 entity
Predicate hasNotableStreet P26446 FINISHED
Object Allegheny Avenue
Allegheny Avenue is a notable street running through the Allegheny West neighborhood of Pittsburgh, Pennsylvania, known for its historic urban character.
E2049416 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: Allegheny Avenue | Statement: [Allegheny West (Pittsburgh), hasNotableStreet, Allegheny 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: Allegheny Avenue
Triple: [Allegheny West (Pittsburgh), hasNotableStreet, Allegheny Avenue]
Generated description
Allegheny Avenue is a notable street running through the Allegheny West neighborhood of Pittsburgh, Pennsylvania, known for its historic urban character.

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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3e24f5081909c2ab8bfe27f3e3a completed May 3, 2026, 5:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3576efc39c8190a6430224aad9ef5a completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a3578b02aa88190b2bb1e4eb311dc60 completed June 19, 2026, 5:13 p.m.
NED2 Entity disambiguation (via description) batch_6a357954f5688190906d3a5c97255922 completed June 19, 2026, 5:16 p.m.
Created at: May 1, 2026, 1:35 a.m.