Triple
T27932645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusheng Festival |
E708024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intangible cultural heritage practice |
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: intangible cultural heritage practice Context triple: [Lusheng Festival, instanceOf, intangible cultural heritage practice]
-
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 practice
A cultural practice is a shared, patterned activity or behavior through which a group expresses, maintains, and transmits its values, beliefs, and social norms.
-
C.
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.
-
D.
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.
-
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.
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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:03 p.m.