Triple
T3674701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Bayside Metromover station |
E77962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automated people mover station |
C538
|
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 station Context triple: [College Bayside Metromover station, instanceOf, automated people mover station]
-
A.
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.
-
B.
people mover system
chosen
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.
-
C.
monorail station
A monorail station is a designated facility where passengers board, alight, and transfer to monorail trains, typically featuring elevated platforms, access structures, and passenger amenities.
-
D.
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.
-
E.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.