Triple
T14518006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadaprabhu Kempegowda Metro Station |
E340574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway station in Bengaluru |
C564
|
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: railway station in Bengaluru Context triple: [Nadaprabhu Kempegowda Metro Station, instanceOf, railway station in Bengaluru]
-
A.
Kolkata Metro station
A Kolkata Metro station is a designated transit facility along the Kolkata Metro network that provides platforms, ticketing, passenger amenities, and access points for boarding and alighting metro trains within the city and its suburbs.
-
B.
Hyderabad Metro station
A Hyderabad Metro station is a designated transit facility within the Hyderabad Metro rail network that enables passengers to board, alight, and transfer between metro services and other modes of transportation.
-
C.
Konkan Railway station
A Konkan Railway station is a designated stop along the Konkan Railway line that provides passenger and freight rail services, facilities, and connectivity to towns and cities along India’s Konkan coast.
-
D.
train station
chosen
A train station is a designated facility where trains regularly stop to pick up and drop off passengers and sometimes freight, typically featuring platforms, ticketing services, and waiting areas.
-
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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.