Triple
T30919267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolnicheskaya Line stations |
E787671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure element collection |
C2822
|
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 element collection Context triple: [Sokolnicheskaya Line stations, instanceOf, transport infrastructure element collection]
-
A.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
B.
transportation corridors collection
chosen
A transportation corridors collection is an organized set of linear pathways—such as roads, railways, and transit routes—grouped for managing, analyzing, or planning movement across a region.
-
C.
transport infrastructure name
A transport infrastructure name identifies a specific facility or network element used for the movement of people or goods, such as a road, railway line, airport, or port.
-
D.
public transportation infrastructure
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.
railway infrastructure element
A railway infrastructure element is any physical component of a rail system—such as tracks, signals, switches, bridges, or platforms—that supports the safe and efficient operation of trains.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.