Triple
T3300688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R11 |
E69323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Subway internal station code |
C1043
|
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 internal station code Context triple: [R11, instanceOf, New York City Subway internal station code]
-
A.
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.
-
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.
IATA-like rail station code
A short, standardized alphanumeric identifier assigned to a railway station, analogous to IATA airport codes, used to uniquely reference stations in timetables, ticketing, and operational systems.
-
D.
railway station code
chosen
A railway station code is a short alphanumeric identifier assigned to a specific train station to uniquely reference it in timetables, ticketing, and railway operations.
-
E.
division of Metropolitan Transportation Authority
A division of the Metropolitan Transportation Authority is an organizational unit responsible for managing and operating a specific set of transit services, assets, or functions within the broader MTA system.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.