Triple
T9455805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgantown Personal Rapid Transit |
E228010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | personal rapid transit system |
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: personal rapid transit system Context triple: [Morgantown Personal Rapid Transit, instanceOf, personal rapid transit system]
-
A.
rapid transit line
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.
-
B.
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.
-
C.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated tracks.
-
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.
rubber-tired transit system
A rubber-tired transit system is a guided public transportation mode in which vehicles run on rubber tires along a dedicated roadway or track, often combining bus-like flexibility with rail-like guidance and capacity.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:52 p.m.