Triple

T9511613
Position Surface form Disambiguated ID Type / Status
Subject Glenmont station E229409 entity
Predicate isTerminusStation P15150 FINISHED
Object yes 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: yes | Statement: [Glenmont station, isTerminusStation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTerminusStation
Context triple: [Glenmont station, isTerminusStation, yes]
  • A. railroadTerminusFor
    Indicates that one location serves as the end point or final station of a particular railroad line for another location.
  • B. terminusStation chosen
    Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
  • C. railLineTerminus
    Indicates that a rail line ends or terminates at the specified location or station.
  • D. isOnlyRailStationServing
    Indicates that one rail station is the sole station providing service to a particular area, route, or entity, with no alternative rail stations serving it.
  • E. isPublicTransportStation
    Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
  • F. None of above.

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_69ca84777560819084cddd999badc1aa completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98699b788190b1a475e1b1883584 completed April 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69cca567ca448190bf4bcce8ce7dd54f completed April 1, 2026, 4:56 a.m.
Created at: March 30, 2026, 7:58 p.m.