Triple
T16198881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Metro Gurgaon |
E393143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light rapid transit system |
C31335
|
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: light rapid transit system Context triple: [Rapid Metro Gurgaon, instanceOf, light rapid transit system]
-
A.
light rail transit line
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
-
B.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
-
C.
light metro
chosen
A light metro is a grade-separated, medium-capacity urban rail transit system that uses smaller trains and shorter headways than full-scale metros to efficiently serve moderate-demand corridors.
-
D.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
E.
light rail vehicle
A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate capacity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:03 a.m.