Triple

T30029431
Position Surface form Disambiguated ID Type / Status
Subject Exposition Light Rail Line project E762971 entity
Predicate instanceOf P0 FINISHED
Object light rail transit project C5215 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: light rail transit project
Context triple: [Exposition Light Rail Line project, instanceOf, light rail transit project]
  • A. light rail expansion project
    A light rail expansion project is a coordinated planning, design, and construction effort to extend an existing light rail transit system’s routes, capacity, and supporting infrastructure to serve additional areas and riders.
  • B. light rail transit line chosen
    A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
  • C. light rail vehicle
    A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate capacity.
  • D. commuter rail project
    A commuter rail project is a coordinated planning, design, and construction effort to develop or improve rail services that transport passengers between suburbs or outlying regions and a central urban area, typically focused on reducing congestion and improving regional mobility.
  • E. rail transit
    Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
Created at: April 29, 2026, 6:49 p.m.