Triple

T4103827
Position Surface form Disambiguated ID Type / Status
Subject SEPTA Route 13 E88401 entity
Predicate terminus P388 FINISHED
Object Yeadon Loop E95580 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: Yeadon Loop | Statement: [SEPTA Route 13, terminus, Yeadon Loop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeadon Loop
Context triple: [SEPTA Route 13, terminus, Yeadon Loop]
  • A. Yeadon Loop chosen
    Yeadon Loop is a trolley turning loop and terminal facility in Yeadon, Pennsylvania, serving as the western endpoint of SEPTA’s Route 13.
  • B. Hindhead
    Hindhead is a village in Surrey, England, known for its elevated position in the Surrey Hills and proximity to the Devil’s Punch Bowl beauty spot.
  • C. Yeadon
    Yeadon is a town in West Yorkshire, England, situated northwest of Leeds and known for its proximity to Leeds Bradford Airport.
  • D. Chadlington
    Chadlington is a rural village in Oxfordshire, England, known for its traditional Cotswold character and surrounding countryside.
  • E. Aylesbury Arm
    The Aylesbury Arm is a narrow canal branch in Buckinghamshire, England, that connects the town of Aylesbury to the main line of the Grand Union Canal.
  • 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_69b56b7a917c8190914a5ffe1297fdc8 completed March 14, 2026, 2:06 p.m.
Created at: March 9, 2026, 3:40 p.m.