Triple
T12289965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North York Heritage Murals |
E292930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage project |
C3129
|
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: cultural heritage project Context triple: [North York Heritage Murals, instanceOf, cultural heritage project]
-
A.
cultural heritage programme
chosen
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
-
B.
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.
-
C.
cultural heritage network
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.
-
D.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
E.
cultural heritage protection system
A cultural heritage protection system is an integrated framework of policies, technologies, and practices designed to identify, preserve, monitor, and safeguard tangible and intangible cultural assets from damage, loss, or unauthorized exploitation.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.