Triple
T873695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connaught Place |
E18870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial and financial district |
C526
|
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: commercial and financial district Context triple: [Connaught Place, instanceOf, commercial and financial district]
-
A.
urban business district
chosen
An urban business district is a densely developed area within a city characterized by a high concentration of offices, commercial activities, financial institutions, and supporting services that form the economic core of the urban environment.
-
B.
commercial historic district
A commercial historic district is a geographically defined area containing a concentration of historically significant commercial buildings and streetscapes that reflect the economic and cultural development of a community over time.
-
C.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
urban plaza
An urban plaza is a publicly accessible open space within a city, typically surrounded by buildings and streets, designed to support social interaction, circulation, and civic activities.
-
E.
entertainment district
An entertainment district is a designated urban area concentrated with venues such as theaters, bars, clubs, restaurants, and other leisure attractions that cater to nightlife and recreational activities.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.