Triple
T20659130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Boulevard–Archer Avenue corridor |
E507709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Subway trunk route |
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 trunk route Context triple: [Queens Boulevard–Archer Avenue corridor, instanceOf, New York City Subway trunk route]
-
A.
New York City Subway tunnel
A New York City Subway tunnel is an underground passageway engineered to safely guide subway trains, utilities, and related infrastructure beneath the city’s surface between stations.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.