Triple

T27489371
Position Surface form Disambiguated ID Type / Status
Subject Fairmount Corridor E693836 entity
Predicate hasTransitServiceType P192554 FINISHED
Object commuter rail corridor LITERAL 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: commuter rail corridor | Statement: [Fairmount Corridor, hasTransitServiceType, commuter rail corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransitServiceType
Context triple: [Fairmount Corridor, hasTransitServiceType, commuter rail corridor]
  • A. hasTransitAccessTo
    Indicates that one place or entity is reachable from another via public or shared transportation services.
  • B. hasPublicTransitServiceLevel
    Indicates the level or quality of public transit service provided to or available at a given location or entity.
  • C. hasBusServices
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • D. hasPublicTransitCoverageType
    Indicates the type or category of public transit service coverage associated with an entity.
  • E. hasCommuterServices
    Indicates that a location or facility provides transportation services specifically intended for regular commuters, such as daily or frequent travelers between home and work or school.
  • F. None of above. chosen

Provenance (4 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_69ef5382b9648190be0b1ef2ad5d043c completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69fd19f791f48190bbb6f6047f9ddc59 completed May 7, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69fd0df365948190bc9bfc7ffd46acd8 completed May 7, 2026, 10:10 p.m.
PDg Predicate description generation batch_69fd19f6a7888190aa7eee2b87687c53 completed May 7, 2026, 11:02 p.m.
Created at: April 27, 2026, 1:04 p.m.