Triple
T16961534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immaterielles Kulturerbe in Deutschland |
E411442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kulturerbe |
C4934
|
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: Kulturerbe Context triple: [Immaterielles Kulturerbe in Deutschland, instanceOf, Kulturerbe]
-
A.
cultural heritage
chosen
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.
-
B.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
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.
artistic heritage site
An artistic heritage site is a location recognized for its enduring cultural, historical, and aesthetic value, preserving significant works of art, architecture, or creative traditions for present and future generations.
-
E.
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.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.