Triple
T12467846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTAB |
E297972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transit operator code |
C31499
|
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: transit operator code Context triple: [MTAB, instanceOf, transit operator code]
-
A.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
-
B.
paratransit operator
A paratransit operator is a transportation service provider that offers flexible, demand-responsive rides—often door-to-door—for individuals whose disabilities or mobility limitations prevent them from using standard public transit.
-
C.
defunct transit operator
A defunct transit operator is a former organization or company that once provided public transportation services but has since ceased operations, often due to financial, regulatory, or structural changes in the transit system.
-
D.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
E.
regional transport office code
A regional transport office code is a standardized alphanumeric identifier assigned to a specific geographic transport authority area, used to uniquely mark and track vehicle registrations and related administrative records.
- F. None of above. chosen
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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.