Triple
T24476665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | метрополитен Санкт-Петербурга |
E617251
|
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 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.
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.
-
D.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
E.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated tracks.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.