Triple
T28415127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhchisarai Historical and Cultural Reserve |
E719781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical and cultural reserve |
C54037
|
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 and cultural reserve Context triple: [Bakhchisarai Historical and Cultural Reserve, instanceOf, historical and cultural reserve]
-
A.
National Historical Reserve
A National Historical Reserve is a protected area that preserves and interprets a significant concentration of historical sites, landscapes, and cultural resources under coordinated management for education, research, and public enjoyment.
-
B.
archaeological reserve
An archaeological reserve is a protected area designated to preserve, study, and manage archaeological sites and artifacts in situ for current and future research and education.
-
C.
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.
-
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.
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.
- F. None of above. chosen
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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:29 a.m.