Triple
T25809644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protohistory galleries |
E650071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage display type |
C51018
|
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 display type Context triple: [Protohistory galleries, instanceOf, cultural heritage display type]
-
A.
cultural heritage object collection
A cultural heritage object collection is an organized assemblage of artifacts, artworks, or historical items preserved and managed to represent and transmit the cultural, historical, or artistic legacy of a community or society.
-
B.
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.
-
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 element
A cultural heritage element is a tangible or intangible manifestation of a community’s traditions, practices, expressions, knowledge, or artifacts that is valued, preserved, and transmitted across generations.
-
E.
cultural heritage experience
A cultural heritage experience is an immersive engagement with the traditions, artifacts, stories, and practices of a community or region that fosters understanding, appreciation, and connection to its historical and contemporary identity.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:08 a.m.