Triple
T20547735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Transport Office Kanpur |
E504516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regional Transport Office |
C43763
|
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: Regional Transport Office Context triple: [Regional Transport Office Kanpur, instanceOf, Regional Transport Office]
-
A.
public transportation agency
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.
-
B.
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.
-
C.
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.
-
D.
rail transport district
A rail transport district is a designated geographic area organized and managed to provide, coordinate, and regulate rail-based transportation services and infrastructure within its boundaries.
-
E.
transport ministry
The transport ministry is a government department responsible for planning, regulating, and overseeing a nation’s transportation systems and infrastructure, including roads, railways, air, and maritime transport.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:38 a.m.