Triple
T18447165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noida Sector 52–Noida Sector 51 (via walkway) |
E450685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metro interchange facility |
C463
|
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 facility Context triple: [Noida Sector 52–Noida Sector 51 (via walkway), instanceOf, metro interchange facility]
-
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.
metro station entrance
A metro station entrance is a designated access point at street level that allows passengers to enter or exit an underground or elevated metro system, typically featuring stairs, escalators, elevators, signage, and fare control access.
-
D.
rapid transit station
chosen
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.
-
E.
tram station
A tram station is a designated stopping place along a tram line where passengers can safely board, alight, and sometimes transfer between tram services.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.