Triple
T11798597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTDC ICTS Mark I |
E280566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automated guided transit vehicle |
C8949
|
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 guided transit vehicle Context triple: [UTDC ICTS Mark I, instanceOf, automated guided transit vehicle]
-
A.
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.
-
B.
automated people mover vehicle
chosen
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.
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.
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.
-
E.
light rail vehicle
A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.