Triple
T670050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine architecture |
E12950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage |
C4934
|
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 Context triple: [Byzantine architecture, instanceOf, cultural heritage]
-
A.
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.
-
B.
cultural heritage designation
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.
-
C.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
-
D.
cultural institution
A cultural institution is an organized establishment, such as a museum, library, theater, or gallery, dedicated to preserving, interpreting, and promoting the arts, heritage, and shared cultural expressions of a community or society.
-
E.
archaeological culture
An archaeological culture is a recurring assemblage of artifacts, features, and other material remains that archaeologists interpret as representing the activities and shared practices of a particular group of people in a specific time and place.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.