Triple
T38083098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | increased public awareness of Treblinka |
E950906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | memory culture development |
C45464
|
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: memory culture development Context triple: [increased public awareness of Treblinka, instanceOf, memory culture development]
-
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.
public memory tradition
chosen
A public memory tradition is a collectively maintained set of stories, symbols, and practices through which a community remembers, interprets, and commemorates its shared past in public spaces and discourse.
-
C.
cultural chronicle
A cultural chronicle is a curated, time-ordered record that documents and interprets the evolving beliefs, practices, artifacts, and social dynamics of a particular culture or group.
-
D.
MassCulture
MassCulture is a conceptual class representing the shared set of ideas, values, practices, and artifacts that are widely disseminated and consumed by large populations through modern mass media and communication technologies.
-
E.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.