Triple

T11023972
Position Surface form Disambiguated ID Type / Status
Subject Charleston station E260566 entity
Predicate servesRouteDirection P12959 FINISHED
Object northbound East Coast long-distance 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: northbound East Coast long-distance routes | Statement: [Charleston station, servesRouteDirection, northbound East Coast long-distance routes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesRouteDirection
Context triple: [Charleston station, servesRouteDirection, northbound East Coast long-distance routes]
  • A. servesDirection chosen
    Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
  • B. routeDirectionB
    Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
  • C. servedByDirection
    Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
  • D. hasRouteDirection
    Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
  • E. routeDirectionA
    Indicates the primary or first directional orientation or heading associated with a specific route.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797be9f148190a3a967bad5947496 completed April 9, 2026, 12:12 p.m.
PD Predicate disambiguation batch_69d72e995e008190bbffb314129ed0cd completed April 9, 2026, 4:44 a.m.
Created at: April 8, 2026, 9:25 p.m.