Triple
T36048312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imaichō historical district |
E1042734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional merchant town |
C61632
|
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: traditional merchant town Context triple: [Imaichō historical district, instanceOf, traditional merchant town]
-
A.
Commercial town
A commercial town is an urban settlement whose primary function and economic activity center on trade, markets, and business services rather than on agriculture or industry.
-
B.
historical trade center
chosen
A historical trade center is a geographically strategic hub where merchants, goods, cultures, and ideas converged over time, driving regional economic activity and cross-cultural exchange.
-
C.
former market town
A former market town is a settlement that historically held regular markets serving as a local commercial hub, but no longer maintains its traditional market functions or status.
-
D.
medieval trading colony
A medieval trading colony is a distant settlement established and controlled by a city or state to facilitate long-distance commerce, resource extraction, and cultural exchange through permanent mercantile presence.
-
E.
former Hanseatic town
A former Hanseatic town is a city that was once a member of the medieval Hanseatic League, historically engaged in extensive maritime trade and governed by shared commercial and legal frameworks.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.