Triple
T13319685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish colonial-style houses at Las Casas Filipinas de Acuzar |
E317282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural heritage collection |
C2724
|
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: architectural heritage collection Context triple: [Spanish colonial-style houses at Las Casas Filipinas de Acuzar, instanceOf, architectural heritage collection]
-
A.
cultural heritage object collection
A cultural heritage object collection is an organized assemblage of artifacts, artworks, or historical items preserved and managed to represent and transmit the cultural, historical, or artistic legacy of a community or society.
-
B.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
C.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
D.
architectural ensemble
chosen
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
E.
serial heritage property
A serial heritage property is a collection of two or more geographically separate but related heritage components that together express a single, coherent cultural or natural significance.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:29 p.m.