Triple

T26110698
Position Surface form Disambiguated ID Type / Status
Subject Cooksville GO Station E658684 entity
Predicate connectsLocalTransit P178755 FINISHED
Object MiWay bus routes 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: MiWay bus routes | Statement: [Cooksville GO Station, connectsLocalTransit, MiWay bus routes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsLocalTransit
Context triple: [Cooksville GO Station, connectsLocalTransit, MiWay bus routes]
  • A. groundTransportConnection
    Indicates a transportation link between locations that is provided via land-based modes such as road or rail.
  • B. publicTransportConnectivity
    Indicates the degree to which locations are linked by accessible and efficient public transportation options.
  • C. operatorOfNearbyTransit
    Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
  • D. providesUrbanTransport
    Indicates that one entity supplies or operates transportation services within an urban or city environment for another entity or the public.
  • E. connectsBoroughTransit
    Indicates a transit link or service that provides direct transportation connectivity between two boroughs.
  • 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_69ee5bc20298819099a42be042eb2349 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f71422adac8190a5ceb32dcf820833 completed May 3, 2026, 9:23 a.m.
PD Predicate disambiguation batch_69f712764d2c819081b64b27e5de4a13 completed May 3, 2026, 9:16 a.m.
PDg Predicate description generation batch_69f71421e8d08190807ccfb15d0f0ddb completed May 3, 2026, 9:23 a.m.
Created at: April 26, 2026, 8:01 p.m.