Triple
T23973813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plane Train automated people mover system |
E604307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underground transit system |
C912
|
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: underground transit system Context triple: [Plane Train automated people mover system, instanceOf, underground transit system]
-
A.
public transit system
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.
-
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.
rail transit
chosen
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.
-
D.
continuous transport system
A continuous transport system is a material handling arrangement that moves goods or resources in an uninterrupted flow along a fixed path using devices such as conveyors, pipelines, or automated tracks.
-
E.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:25 p.m.