Triple
T19438054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R29 |
E486275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Subway station code |
C41757
|
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 station code Context triple: [R29, instanceOf, New York City Subway station code]
-
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.
Amtrak station code
An Amtrak station code is a unique three-letter identifier assigned to each train station served by Amtrak for use in reservations, ticketing, and operations.
-
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.
New York City Subway transfer connection
A New York City Subway transfer connection is a designated pathway or arrangement that allows passengers to move between different subway lines or stations within a single fare, facilitating efficient route changes and network connectivity.
-
E.
New York City Subway rolling stock class
A New York City Subway rolling stock class is a standardized group of subway cars sharing common design, technical specifications, and operational characteristics used on the NYC subway system.
- F. None of above. chosen
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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.