Triple
T5909791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colombo Municipal Council area |
E131430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban administrative area |
C19533
|
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 administrative area Context triple: [Colombo Municipal Council area, instanceOf, urban administrative area]
-
A.
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.
-
B.
metropolitan area
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.
inner-city area
An inner-city area is a densely populated, centrally located urban district typically characterized by older infrastructure, mixed residential and commercial land use, and often higher levels of socioeconomic challenges.
-
D.
urban-type settlement
An urban-type settlement is a semi-urban locality that exhibits some characteristics of a town or small city—such as concentrated housing, infrastructure, and non-agricultural employment—without meeting all the criteria for full city status.
-
E.
urban centre
An urban centre is a densely populated area characterized by concentrated human settlement, infrastructure, services, and economic activities that serve as a focal point for surrounding regions.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.