Triple
T7862264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake City (Bidhannagar) |
E182527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned satellite township |
C22
|
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: planned satellite township Context triple: [Salt Lake City (Bidhannagar), instanceOf, planned satellite township]
-
A.
planned city
chosen
A planned city is an urban area whose layout, infrastructure, and land use are deliberately designed and constructed according to a comprehensive plan before significant settlement occurs.
-
B.
planned residential community
A planned residential community is a deliberately designed neighborhood or development where housing, infrastructure, amenities, and land use are pre-organized to create a cohesive living environment.
-
C.
town plan
A town plan is a comprehensive design that organizes the spatial layout, land use, infrastructure, and public spaces of a town to guide its development and functioning.
-
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.
experimental township
An experimental township is a deliberately planned community designed to test innovative social, economic, environmental, or governance models on a small scale before broader implementation.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:53 p.m.