Triple
T32335634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheapside market area |
E826163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval marketplace |
C61399
|
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: medieval marketplace Context triple: [Cheapside market area, instanceOf, medieval marketplace]
-
A.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
B.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
C.
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.
-
D.
medieval march
A medieval march is a border territory or frontier region of a kingdom or empire, governed by a margrave or similar official, established to defend against external threats and manage cross-border relations.
-
E.
medieval charm
A medieval charm is a small, often inscribed object or spoken formula believed to harness supernatural or divine power for protection, healing, or influencing events in accordance with medieval beliefs and practices.
- F. None of above. chosen
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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:48 a.m.