Triple
T23396266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheduled monuments in Scotland |
E559367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site protection regime |
C15462
|
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: archaeological site protection regime Context triple: [Scheduled monuments in Scotland, instanceOf, archaeological site protection regime]
-
A.
archaeological site protection
chosen
Archaeological site protection is the practice of identifying, preserving, and managing locations with archaeological significance to safeguard their cultural, historical, and scientific value from damage, looting, and destruction.
-
B.
archaeological site record
An archaeological site record is a structured documentation of an archaeological location, detailing its features, artifacts, context, chronology, and research history for preservation and study.
-
C.
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.
-
D.
cultural heritage protection system
A cultural heritage protection system is an integrated framework of policies, technologies, and practices designed to identify, preserve, monitor, and safeguard tangible and intangible cultural assets from damage, loss, or unauthorized exploitation.
-
E.
archaeological site collection
An archaeological site collection is an organized assemblage of artifacts, ecofacts, records, and related materials systematically gathered from one or more archaeological sites for study, preservation, and interpretation.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:36 p.m.