Triple
T5631932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canmore database |
E147853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage database |
C12523
|
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 database Context triple: [Canmore database, instanceOf, heritage database]
-
A.
cultural heritage database
chosen
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.
-
B.
heritage centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
-
C.
cultural heritage
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
-
D.
cultural heritage survey
A cultural heritage survey is a systematic assessment and documentation of a community’s tangible and intangible cultural resources to understand, preserve, and manage them for present and future generations.
-
E.
heritage conservation document
A heritage conservation document is a formal record that outlines the historical significance, current condition, and recommended preservation strategies for a cultural heritage site, object, or landscape.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:40 p.m.