Triple
T13531966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTA service information materials |
E323154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transportation information material |
C11180
|
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: public transportation information material Context triple: [MTA service information materials, instanceOf, public transportation information material]
-
A.
public transportation infrastructure
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.
-
B.
public transport information system
chosen
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.
-
C.
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.
-
D.
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.
-
E.
public transit board
A public transit board is a governing body responsible for overseeing, setting policy for, and making strategic decisions about a region’s public transportation system.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.