Triple
T23666360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | central canal belt of Amsterdam |
E584588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic city center area |
C32895
|
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 city center area Context triple: [central canal belt of Amsterdam, instanceOf, historic city center area]
-
A.
historic city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
-
B.
historic urban center
chosen
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
-
C.
historic city square
A historic city square is a central public open space in a town or city, typically surrounded by significant buildings and monuments, that has served as a focal point for social, political, and commercial activities over time.
-
D.
historic town centre
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.
-
E.
immersive historical center
An immersive historical center is an interactive, multisensory environment that uses exhibits, reenactments, and technology to transport visitors into past eras and bring historical events and cultures vividly to 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.