Triple
T28810579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolkata metropolitan transport region |
E727501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban agglomeration transport area |
C61
|
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: urban agglomeration transport area Context triple: [Kolkata metropolitan transport region, instanceOf, urban agglomeration transport area]
-
A.
urban administrative area
An urban administrative area is a geographically defined part of a city or town governed by specific local authorities responsible for public services, regulation, and planning within its boundaries.
-
B.
metropolitan area
chosen
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
-
C.
urban system
An urban system is an interconnected network of cities and their surrounding regions, encompassing the flows of people, goods, information, and resources that shape their social, economic, and environmental dynamics.
-
D.
urban service area
An urban service area is a designated geographic zone within or around a city where public services and infrastructure—such as water, sewer, transportation, and emergency response—are planned, provided, and managed in a coordinated manner.
-
E.
transit-oriented development area
A transit-oriented development area is a compact, walkable, mixed-use urban district planned around high-quality public transportation to reduce car dependence and support sustainable living.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:30 a.m.