Triple
T27849775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLS (DS100 code for S-Bahn/rail) |
E703918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DS100 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: DS100 station code Context triple: [BLS (DS100 code for S-Bahn/rail), instanceOf, DS100 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.
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.
-
C.
Tokyo Metro station code
A Tokyo Metro station code is a concise alphanumeric identifier that uniquely represents each station on the Tokyo Metro network, typically combining a line letter with a station number to simplify navigation and mapping.
-
D.
New York City Subway station code
A New York City Subway station code is a unique alphanumeric identifier assigned to each subway station to standardize reference, operations, and data management across the transit system.
-
E.
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.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:09 p.m.