Triple
T1728394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oudezijds Achterburgwal |
E37552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic district feature |
C9177
|
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 district feature Context triple: [Oudezijds Achterburgwal, instanceOf, historic district feature]
-
A.
historic market district
A historic market district is a preserved urban area where traditional marketplaces, architecture, and cultural practices converge to reflect the commercial and social life of a community across time.
-
B.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
C.
historic legal precinct
A historic legal precinct is a designated urban area containing significant past and present legal institutions—such as courts, law offices, and civic buildings—preserved for their architectural, cultural, and judicial heritage.
-
D.
commercial historic district
A commercial historic district is a geographically defined area containing a concentration of historically significant commercial buildings and streetscapes that reflect the economic and cultural development of a community over time.
-
E.
historic institution
A historic institution is an established organization or structure that has played a significant, enduring role in society over time and is recognized for its cultural, political, or social legacy.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.