Triple
T32135375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CentralAsianCuisine |
E820752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intangibleCulturalHeritage |
C5683
|
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: intangibleCulturalHeritage Context triple: [CentralAsianCuisine, instanceOf, intangibleCulturalHeritage]
-
A.
intangible cultural heritage
chosen
Intangible cultural heritage refers to the practices, expressions, knowledge, and skills that communities recognize as part of their cultural identity and transmit from generation to generation.
-
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 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.
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 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.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:30 a.m.