Triple
T15482291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaroslavsky railway station, Moscow |
E376948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure in Moscow |
C2489
|
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: transport infrastructure in Moscow Context triple: [Yaroslavsky railway station, Moscow, instanceOf, transport infrastructure in Moscow]
-
A.
road in Moscow
A road in Moscow is a transportation route within the city’s urban network that facilitates vehicular and pedestrian movement between various districts, landmarks, and infrastructure.
-
B.
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.
-
C.
Moscow Metro depot
A Moscow Metro depot is a specialized facility where metro trains are stored, inspected, maintained, and repaired to ensure reliable operation of the Moscow subway system.
-
D.
public transportation infrastructure
chosen
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
E.
bridge in Moscow
A bridge in Moscow is a structural crossing over the Moskva River or other waterways in the city, serving both transportation needs and often acting as an architectural landmark within the urban landscape.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:38 a.m.