Triple
T26076683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Baltimore |
E657703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban economy |
C51082
|
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 economy Context triple: [Economy of Baltimore, instanceOf, urban economy]
-
A.
urban economic impact zone
An urban economic impact zone is a designated area within a city where targeted policies, investments, and regulations are applied to stimulate economic activity, attract businesses, and improve local employment and infrastructure.
-
B.
urban development
Urban development is the planned growth and improvement of cities and towns through the design, regulation, and construction of buildings, infrastructure, and public spaces to support economic, social, and environmental needs.
-
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 estate
An urban estate is a sizable residential or mixed-use property situated within a city, typically comprising multiple buildings, shared amenities, and managed grounds designed for dense, organized urban living.
-
E.
urban business district
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.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:34 p.m.