Triple
T2134867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlem Line |
E46626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Metro-North Railroad line |
C74
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Metro-North Railroad line Context triple: [Harlem Line, instanceOf, Metro-North Railroad line]
-
A.
Long Island Rail Road service area
The Long Island Rail Road service area encompasses the network of commuter rail lines and stations extending from New York City through Nassau and Suffolk counties on Long Island, providing passenger rail service to communities across this region.
-
B.
MBTA Commuter Rail station
An MBTA Commuter Rail station is a designated passenger facility along the Massachusetts Bay Transportation Authority’s regional rail network where trains stop to allow riders to board, alight, and connect with other modes of transit.
-
C.
commuter rail line
chosen
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
D.
New York City Subway–railroad interchange
A New York City Subway–railroad interchange is a facility or location where subway lines physically connect with or provide direct transfer to mainline or commuter rail services, enabling passenger and sometimes equipment movement between the two systems.
-
E.
subway line
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
- F. None of above.
Provenance (1 batch)
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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:44 p.m.