Triple
T27859711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mira-Bhayandar Municipal Transport |
E704190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal transport undertaking |
C220
|
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: municipal transport undertaking Context triple: [Mira-Bhayandar Municipal Transport, instanceOf, municipal transport undertaking]
-
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.
public transportation agency
chosen
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
C.
Regional Transport Office
A Regional Transport Office is a government agency responsible for vehicle registration, driver licensing, enforcement of transport regulations, and maintenance of regional motor vehicle records.
-
D.
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.
-
E.
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.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:16 p.m.