Triple
T35689194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Street Breckenridge |
E1031242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | downtown commercial corridor |
C15040
|
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: downtown commercial corridor Context triple: [Main Street Breckenridge, instanceOf, downtown commercial corridor]
-
A.
neighborhood corridor
A neighborhood corridor is a linear, mixed-use area within a community that concentrates housing, shops, services, and transportation along a primary street to support walkability and local activity.
-
B.
urban retail corridor system
An urban retail corridor system is a network of interconnected commercial streets, storefronts, public spaces, and supporting infrastructure that collectively organize, concentrate, and facilitate pedestrian-oriented shopping, services, and social activity within a city.
-
C.
urban promenade
An urban promenade is a designed public walkway or boulevard in a city, intended for leisurely strolling, social interaction, and visual enjoyment of the surrounding urban landscape.
-
D.
pedestrian-oriented commercial district
chosen
A pedestrian-oriented commercial district is a compact, walkable area where shops, services, and public spaces are clustered and designed primarily for people on foot rather than for automobile access.
-
E.
group of central business districts
A group of central business districts is a collection of geographically distinct urban cores where commercial, financial, and administrative activities are highly concentrated and functionally interconnected.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.