Triple

T20059828
Position Surface form Disambiguated ID Type / Status
Subject MARTA color-based naming scheme E499438 entity
Predicate instanceOf P0 FINISHED
Object public transportation branding system C7634 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 branding system
Context triple: [MARTA color-based naming scheme, instanceOf, public transportation branding 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. 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.
  • C. 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.
  • D. public transit brand chosen
    A public transit brand is the cohesive identity—encompassing name, visuals, messaging, and perceived values—that distinguishes a transit agency’s services and shapes how riders recognize, trust, and experience the system.
  • E. streetcar system
    A streetcar system is an urban public transit network that operates rail vehicles on fixed tracks, typically embedded in city streets, to transport passengers along defined routes.
  • 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
Created at: April 11, 2026, 3:38 p.m.