Triple
T9101087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolnichesky Radius Interchange Stations |
E218154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of metro interchange stations |
C25595
|
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: group of metro interchange stations Context triple: [Sokolnichesky Radius Interchange Stations, instanceOf, group of metro interchange stations]
-
A.
railway–metro interchange
A railway–metro interchange is a transport facility where mainline railway services and urban metro lines connect, enabling passengers to transfer conveniently between regional and local rail networks.
-
B.
group of light rail stations
A group of light rail stations is a collection of geographically or operationally related stops along a light rail transit line or network, treated as a single unit for planning, analysis, or management purposes.
-
C.
group of passenger rail terminals
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
-
D.
Shanghai Metro station
A Shanghai Metro station is a designated public transit facility within the Shanghai Metro network where passengers access, board, transfer between, and alight from metro trains.
-
E.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:15 p.m.