Triple
T11276311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia City business district |
E266946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic business district |
C3823
|
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: historic business district Context triple: [Columbia City business district, instanceOf, historic business district]
-
A.
historic market district
A historic market district is a preserved urban area where traditional marketplaces, architecture, and cultural practices converge to reflect the commercial and social life of a community across time.
-
B.
commercial historic district
chosen
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.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
D.
historic commercial building
A historic commercial building is a long-standing structure originally designed and used for business or trade that holds architectural, cultural, or historical significance.
-
E.
historic city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.