Triple
T35970966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izborsk State Museum-Reserve |
E1040283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical and cultural complex |
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 complex Context triple: [Izborsk State Museum-Reserve, instanceOf, historical and cultural complex]
-
A.
historical and cultural reserve
chosen
A historical and cultural reserve is a protected area that preserves and showcases significant historical sites, architectural monuments, and cultural heritage within a unified territorial complex.
-
B.
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.
-
C.
Baroque pilgrimage complex
A Baroque pilgrimage complex is an architecturally unified ensemble of churches, chapels, and ancillary structures, often dramatically sited in the landscape, designed to guide and intensify the spiritual journey of pilgrims through processional routes, symbolic spaces, and theatrical visual effects.
-
D.
heritage building complex
A heritage building complex is a group of historically or culturally significant structures and associated spaces that are preserved and managed together as a unified cultural asset.
-
E.
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.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.