Triple

T4103839
Position Surface form Disambiguated ID Type / Status
Subject SEPTA Route 13 E88401 entity
Predicate usesStreet P17242 FINISHED
Object Chester Avenue E32860 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: Chester Avenue | Statement: [SEPTA Route 13, usesStreet, Chester Avenue]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chester Avenue
Context triple: [SEPTA Route 13, usesStreet, Chester Avenue]
  • A. Chester Avenue chosen
    Chester Avenue is a major street in Philadelphia that serves as part of the surface-running route for SEPTA’s Subway–Surface trolley lines.
  • B. Church Avenue
    Church Avenue is a central street in downtown Knoxville, Tennessee, known for connecting key civic, commercial, and historic areas of the city’s urban core.
  • C. Church Avenue
    Church Avenue is a New York City Subway station in Brooklyn that serves as the southern terminal for the G train.
  • D. Lancaster Avenue
    Lancaster Avenue is a major thoroughfare in Philadelphia that serves as a key commercial and transit corridor through the University City area and beyond.
  • E. Concord Avenue
    Concord Avenue is a principal roadway running through Belmont, Massachusetts, serving as a key thoroughfare in the Belmont Center area and its historic district.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69aed9484fb881909146f4c772ad277c completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefd31bad88190b850d1dcba14de60 completed March 9, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8108dda308190bb3b7209efe132bb completed March 28, 2026, 5:31 p.m.
Created at: March 9, 2026, 3:40 p.m.