Triple
T37925611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmonte Calabro historic centre |
E946083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval town centre |
C14156
|
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 town centre Context triple: [Belmonte Calabro historic centre, instanceOf, medieval town centre]
-
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.
historic town centre
chosen
A historic town centre is the traditional core of a town characterized by preserved architecture, cultural landmarks, and public spaces that reflect its historical development and heritage.
-
C.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
-
D.
medieval capital
A medieval capital is the carved topmost element of a column or pillar in Middle Ages architecture, often richly decorated with foliage, figures, or symbolic motifs to transition between the shaft and the structure it supports.
-
E.
medieval marketplace
A medieval marketplace is a bustling open-air trading hub where merchants, peasants, and travelers gather to buy, sell, and barter goods amid lively sounds, vivid smells, and the backdrop of town life.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.