Triple
T30219048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 重庆轨道交通 |
E768289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 快速交通系统 |
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: 快速交通系统 Context triple: [重庆轨道交通, instanceOf, 快速交通系统]
-
A.
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.
-
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.
high-speed railway
A high-speed railway is a rail transport system designed for trains that operate at significantly higher speeds than traditional rail services, typically on specially built or upgraded tracks, to provide fast, efficient, and reliable long-distance passenger travel.
-
D.
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.
-
E.
proposed high-speed ground transportation system
A proposed high-speed ground transportation system is a conceptual network of advanced vehicles, infrastructure, and control technologies designed to move passengers or freight rapidly and efficiently between destinations along dedicated terrestrial corridors.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:34 p.m.