Triple
T37065905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base Mérimée |
E917442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural heritage inventory |
C47508
|
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 inventory Context triple: [Base Mérimée, instanceOf, architectural heritage inventory]
-
A.
heritage inventory program
chosen
A heritage inventory program is a systematic initiative to identify, document, and evaluate cultural, historical, and natural heritage resources within a defined area for their protection, management, and public awareness.
-
B.
architectural survey
An architectural survey is a systematic assessment and documentation of a building or site’s physical condition, design features, and historical or regulatory context to inform planning, preservation, or construction decisions.
-
C.
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.
-
D.
historic building record
A historic building record is a documented account that captures the architectural, cultural, and historical details of a building, including its design, construction, alterations, significance, and preservation status.
-
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.