Triple
T21864935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Heritage Information Network |
E539859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage information network |
C25984
|
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 information network Context triple: [Canadian Heritage Information Network, instanceOf, heritage information network]
-
A.
cultural heritage network
chosen
A cultural heritage network is a connected system of institutions, communities, and digital platforms that collaboratively preserve, share, and promote cultural artifacts, traditions, and knowledge across regions and generations.
-
B.
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.
-
C.
cultural heritage aggregator
A cultural heritage aggregator is a system that collects, harmonizes, and provides unified access to cultural artifacts, records, and metadata from multiple institutions and sources.
-
D.
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.
-
E.
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.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 6:56 p.m.