Triple
T20487353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peru Downtown Historic District |
E502633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic commercial center |
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 commercial center Context triple: [Peru Downtown Historic District, instanceOf, historic commercial center]
-
A.
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.
-
B.
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.
-
C.
former commercial centre
A former commercial centre is a once-prominent hub of trade and business activity that has since declined or shifted in economic importance, often leaving behind historical infrastructure and altered urban functions.
-
D.
historic urban center
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
-
E.
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.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:34 a.m.