Triple
T29919162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic City Centre of Braunschweig |
E759873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval town core |
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 core Context triple: [Historic City Centre of Braunschweig, instanceOf, medieval town core]
-
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 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.
-
C.
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.
-
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 urban system
A medieval urban system is the interconnected network of towns and cities, their institutions, economic activities, social hierarchies, and spatial arrangements that structured urban life and regional interactions in the Middle Ages.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:13 p.m.