Triple
T29467939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuri Gagarin memorial sites |
E747430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage theme |
C25050
|
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 theme Context triple: [Yuri Gagarin memorial sites, instanceOf, cultural heritage theme]
-
A.
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.
-
B.
cultural heritage element
chosen
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.
-
C.
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.
-
D.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:54 p.m.