Triple
T8754502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhny Novgorod Cableway |
E208040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban cable car line |
C1080
|
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 cable car line Context triple: [Nizhny Novgorod Cableway, instanceOf, urban cable car line]
-
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.
cable car system
chosen
A cable car system is a transportation network in which vehicles are pulled by continuously moving cables, typically used to move people or goods along steep or inaccessible routes such as mountainsides or urban hills.
-
C.
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.
-
D.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
E.
monorail-served city
A monorail-served city is an urban area whose public transportation network prominently features one or more elevated monorail lines that provide regular passenger service and integrate with the city’s overall mobility system.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:39 p.m.