Triple
T20643419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lefferts Boulevard branch |
E507287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Subway service branch |
C641
|
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: New York City Subway service branch Context triple: [Lefferts Boulevard branch, instanceOf, New York City Subway service branch]
-
A.
New York City Subway service designation
A New York City Subway service designation is a letter, number, or symbol that identifies a specific subway route, indicating its line, terminals, and general service pattern for riders.
-
B.
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.
-
C.
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.
-
D.
subway line
chosen
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.
-
E.
Long Island Rail Road line
A Long Island Rail Road line is a specific passenger rail route within the LIRR network that connects designated terminals and intermediate stations across Long Island and the greater New York City area.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.