Triple
T12675432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Liner |
E302798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | driverless urban transit line |
C13192
|
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: driverless urban transit line Context triple: [Port Liner, instanceOf, driverless urban transit line]
-
A.
urban transit technology
Urban transit technology encompasses the systems, vehicles, infrastructure, and digital tools that enable efficient, safe, and sustainable movement of people within cities.
-
B.
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.
-
C.
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.
-
D.
automated guideway transit line
chosen
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.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.