Triple
T22182100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Cambridge Museums |
E548194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage organisation |
C45903
|
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 organisation Context triple: [University of Cambridge Museums, instanceOf, cultural heritage organisation]
-
A.
heritage conservation organization
A heritage conservation organization is an entity dedicated to identifying, protecting, preserving, and promoting cultural, historical, and natural heritage resources for present and future generations.
-
B.
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.
-
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.
World Heritage Centre
The World Heritage Centre is an organization or entity responsible for identifying, protecting, and managing cultural and natural sites of outstanding universal value around the globe.
-
E.
cultural heritage management sector
The cultural heritage management sector encompasses organizations and professionals dedicated to preserving, interpreting, and sustainably managing tangible and intangible cultural resources for present and future generations.
- F. None of above. chosen
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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.