Triple
T32992206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi urban rail and metro corridors |
E844115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban rail network plan |
C31796
|
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: urban rail network plan Context triple: [Hanoi urban rail and metro corridors, instanceOf, urban rail network plan]
-
A.
urban rail loop line
An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
-
B.
rapid transit network
chosen
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
-
C.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
D.
planned public transit line
A planned public transit line is a proposed, not-yet-built transportation route with defined stops, alignment, and service characteristics intended for future public operation.
-
E.
commuter rail project
A commuter rail project is a coordinated planning, design, and construction effort to develop or improve rail services that transport passengers between suburbs or outlying regions and a central urban area, typically focused on reducing congestion and improving regional mobility.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.