Triple

T2267312
Position Surface form Disambiguated ID Type / Status
Subject Moscow Central Diameters E50176 entity
Predicate instanceOf P0 FINISHED
Object public transport network component C911 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: public transport network component
Context triple: [Moscow Central Diameters, instanceOf, public transport network component]
  • A. transportation network company
    A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
  • B. 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.
  • C. public transit system chosen
    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.
  • D. 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.
  • E. transport infrastructure operator
    A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
  • 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_69a88b01e0048190ba96431b5f990ba9 completed March 4, 2026, 7:41 p.m.
Created at: March 4, 2026, 7:48 p.m.