Triple
T4146127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemnitz Zentralhaltestelle |
E89786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tram and bus interchange |
C7253
|
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: tram and bus interchange Context triple: [Chemnitz Zentralhaltestelle, instanceOf, tram and bus interchange]
-
A.
public transit station
chosen
A public transit station is a designated facility where passengers can access, board, transfer between, and disembark from public transportation services such as buses, trains, or subways.
-
B.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
C.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
D.
trolleybus stop
A trolleybus stop is a designated roadside area where trolleybuses halt to safely pick up and drop off passengers, typically marked with signage and sometimes shelters or platforms.
-
E.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:43 p.m.