Triple

T17735030
Position Surface form Disambiguated ID Type / Status
Subject Fifth Avenue (Pittsburgh) E442690 entity
Predicate partOf P40 FINISHED
Object Pittsburgh street network NE NERFINISHED

How this triple was built (3 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: Pittsburgh street network | Statement: [Fifth Avenue (Pittsburgh), partOf, Pittsburgh street network]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pittsburgh street network
Context triple: [Fifth Avenue (Pittsburgh), partOf, Pittsburgh street network]
  • A. Philadelphia street network
    The Philadelphia street network is the interconnected system of roads, avenues, and thoroughfares that structure transportation and urban layout across the city of Philadelphia and its surrounding areas.
  • B. Baltimore street network
    The Baltimore street network is the interconnected system of roads, streets, and thoroughfares that structure transportation, navigation, and urban layout within the city of Baltimore, Maryland.
  • C. Portland street network
    The Portland street network is the interconnected system of roads, avenues, and transit corridors that structure transportation and urban movement throughout Portland, Oregon.
  • D. Oakland street network
    The Oakland street network is the interconnected system of roads, streets, and thoroughfares that supports vehicular, transit, cycling, and pedestrian movement throughout the city of Oakland, California.
  • E. South Philadelphia street network
    The South Philadelphia street network is an urban grid of major and minor streets in the southern part of Philadelphia, Pennsylvania, known for its dense residential blocks, commercial corridors, and industrial waterfront access.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Pittsburgh street network
Target entity description: The Pittsburgh street network is the complex system of roads and thoroughfares that weaves through Pittsburgh’s hilly terrain and river valleys, connecting its diverse neighborhoods and business districts.
  • A. Philadelphia street network
    The Philadelphia street network is the interconnected system of roads, avenues, and thoroughfares that structure transportation and urban layout across the city of Philadelphia and its surrounding areas.
  • B. Baltimore street network
    The Baltimore street network is the interconnected system of roads, streets, and thoroughfares that structure transportation, navigation, and urban layout within the city of Baltimore, Maryland.
  • C. Portland street network
    The Portland street network is the interconnected system of roads, avenues, and transit corridors that structure transportation and urban movement throughout Portland, Oregon.
  • D. Oakland street network
    The Oakland street network is the interconnected system of roads, streets, and thoroughfares that supports vehicular, transit, cycling, and pedestrian movement throughout the city of Oakland, California.
  • E. South Philadelphia street network
    The South Philadelphia street network is an urban grid of major and minor streets in the southern part of Philadelphia, Pennsylvania, known for its dense residential blocks, commercial corridors, and industrial waterfront access.
  • F. None of above. chosen

Provenance (2 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e478e98a00819089490be2aa36873d completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 10:08 a.m.