Triple
T37370650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state historical and cultural reserve of Ukraine |
E927833
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical heritage protection category |
C827
|
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: historical heritage protection category Context triple: [state historical and cultural reserve of Ukraine, instanceOf, historical heritage protection category]
-
A.
protected heritage area
A protected heritage area is a designated geographic space preserved and managed to safeguard its cultural, historical, or natural significance for present and future generations.
-
B.
heritage preserve
A heritage preserve is a protected area designated to conserve and manage significant natural, cultural, or historical resources for present and future generations.
-
C.
cultural heritage designation
chosen
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
-
D.
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.
-
E.
heritage protection system element
A heritage protection system element is a component—such as a policy, structure, technology, or procedure—designed to prevent damage, loss, or degradation of cultural or natural heritage assets.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.