Triple
T32397420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Znamenskaya Church site |
E827848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage location |
C3208
|
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 location Context triple: [Znamenskaya Church site, instanceOf, cultural heritage location]
-
A.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
B.
cultural heritage monument
chosen
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.
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.
-
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 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.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:52 a.m.