Triple

T2631709
Position Surface form Disambiguated ID Type / Status
Subject Line 7 (planned) E59645 entity
Predicate instanceOf P0 FINISHED
Object planned metro line C640 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: planned metro line
Context triple: [Line 7 (planned), instanceOf, planned metro line]
  • A. subway line
    A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
  • B. urban rail loop line
    An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
  • C. light rail transit line
    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.
  • D. monorail transit line
    A monorail transit line is an elevated or ground-level guided transportation system in which trains run on a single rail, typically used for urban or campus passenger service.
  • E. rapid transit line chosen
    A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
  • 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_69ab4ac8596c8190b34997e73d9e991c completed March 6, 2026, 9:44 p.m.
Created at: March 6, 2026, 9:50 p.m.