Triple
T16140741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardinian heraldry |
E391646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage of Sardinia |
C25050
|
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 of Sardinia Context triple: [Sardinian heraldry, instanceOf, cultural heritage of Sardinia]
-
A.
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.
-
B.
nuragic archaeological site
A nuragic archaeological site is a prehistoric complex in Sardinia characterized by stone towers (nuraghi), villages, tombs, and ritual structures built by the Nuragic civilization between the Bronze and Iron Ages.
-
C.
Sardinian legal code
A Sardinian legal code is a structured body of laws and regulations historically or currently governing social, economic, and political life in Sardinia, reflecting its unique cultural, linguistic, and institutional traditions.
-
D.
cultural heritage element
chosen
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.
-
E.
Ligurian settlement
A Ligurian settlement is a historically or archaeologically identified inhabited place established or predominantly occupied by the ancient Ligurian people, characterized by their distinct cultural, social, and territorial attributes.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:01 a.m.