Triple
T31918198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Проспект Вернадского |
E814893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | проспект Москвы |
C57610
|
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.
Moscow Central Diameters line
The Moscow Central Diameters line is a suburban rail transit route in Moscow that operates like an urban through-running commuter line, connecting outlying areas across the city via upgraded existing railway corridors.
-
B.
Moscow Central Circle station
A Moscow Central Circle station is a passenger rail facility on Moscow's orbital urban rail line that provides platforms, services, and access for trains and commuters within the city's integrated transit network.
-
C.
Saint Petersburg Metro line
A Saint Petersburg Metro line is a distinct rapid transit route within the Saint Petersburg Metro system, consisting of a series of interconnected stations and tracks that provide high-capacity urban rail transport along a defined corridor.
-
D.
Moscow Monorail station
A Moscow Monorail station is a designated stop along the Moscow Monorail system where passengers can board, alight, and transfer between monorail trains and other modes of public transportation.
-
E.
Sofia Metro station
A Sofia Metro station is an underground or surface transit facility within the Sofia Metro system that provides platforms, access points, and related infrastructure for boarding, alighting, and transferring between metro trains.
- F. None of above. chosen
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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:02 a.m.