Triple
T4074217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jirón de la Unión |
E86722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic district street |
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 district street Context triple: [Jirón de la Unión, instanceOf, historic district street]
-
A.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural 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.
historic road
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
D.
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.
-
E.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.