Triple

T13336916
Position Surface form Disambiguated ID Type / Status
Subject Queens Road station E317718 entity
Predicate instanceOf P0 FINISHED
Object transport infrastructure name C32846 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 name
Context triple: [Queens Road station, instanceOf, transport infrastructure name]
  • 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. transport corridor
    A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
  • C. road transport node
    A road transport node is a specific location within a road network where vehicles and travelers converge, diverge, or transfer, such as intersections, terminals, or hubs.
  • 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. road infrastructure
    Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
  • F. None of above. chosen

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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
Created at: April 9, 2026, 9:31 p.m.