Triple
T29918614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt Institute intercampus transportation system |
E759858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercampus transportation system |
C2489
|
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: intercampus transportation system Context triple: [Pratt Institute intercampus transportation system, instanceOf, intercampus transportation system]
-
A.
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.
-
B.
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.
-
C.
public transportation infrastructure
chosen
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
D.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
E.
campus axis
A campus axis is a primary organizing line or pathway that structures the spatial layout, circulation, and visual relationships of buildings and open spaces across a campus.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:13 p.m.