Triple
T36519638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adtranz–Bombardier ART trains (earlier stock) |
E900141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automated light rail 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 light rail vehicle Context triple: [Adtranz–Bombardier ART trains (earlier stock), instanceOf, automated light rail vehicle]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
light rail transit line
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.