Triple
T22407222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Hospital Shopping Precinct |
E553908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage building complex |
C46239
|
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: heritage building complex Context triple: [Dutch Hospital Shopping Precinct, instanceOf, heritage building complex]
-
A.
civic building complex
A civic building complex is a coordinated group of public structures and spaces designed to house governmental, administrative, and community services within a unified physical setting.
-
B.
museum building complex
A museum building complex is a coordinated group of structures and spaces designed to collect, preserve, exhibit, and interpret cultural, historical, artistic, or scientific artifacts for public education and enjoyment.
-
C.
stone-built architectural complex
A stone-built architectural complex is a cohesive group of structures primarily constructed from stone, designed to function together as an integrated spatial and functional whole.
-
D.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
E.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.