Triple
T20764534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Loop Metromover |
E511059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automated people mover route |
C32528
|
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: automated people mover route Context triple: [Inner Loop Metromover, instanceOf, automated people mover route]
-
A.
people mover system
A people mover system is an automated transportation network designed to efficiently move passengers over short to medium distances within confined areas such as airports, campuses, or urban centers.
-
B.
automated people mover vehicle
An automated people mover vehicle is a driverless, guided transit vehicle designed to transport passengers along a fixed route within confined areas such as airports, campuses, or urban centers.
-
C.
automated guideway transit line
An automated guideway transit line is a fully automated, driverless rail or rubber-tired transit system operating on a dedicated guideway, typically used for short- to medium-distance urban or campus circulation.
-
D.
Metromover route
chosen
A Metromover route is a predefined path within an automated downtown transit system that specifies the sequence of stations and track segments a Metromover vehicle follows to provide passenger service.
-
E.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:36 p.m.