Triple
T21922894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Capitol Subway System |
E541364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underground people mover system |
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: underground people mover system Context triple: [United States Capitol Subway System, instanceOf, underground people mover system]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
underground rail corridor
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:45 p.m.