Triple
T9719507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevsky Prospekt–Gostiny Dvor metro hub |
E235427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metro interchange complex |
C82
|
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: metro interchange complex Context triple: [Nevsky Prospekt–Gostiny Dvor metro hub, instanceOf, metro interchange complex]
-
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 metro interchange stations
A group of metro interchange stations is a collection of transit hubs where multiple metro lines intersect, enabling passengers to transfer between routes within an urban rail network.
-
C.
combined civic building and transportation hub
A combined civic building and transportation hub is a multifunctional public facility that integrates government or community services with major transit infrastructure to centralize access, improve connectivity, and enhance urban efficiency.
-
D.
transport hub
chosen
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
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.
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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:20 p.m.