Triple
T22116808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SK |
E546565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site code |
C45822
|
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 code Context triple: [SK, instanceOf, archaeological site code]
-
A.
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.
-
B.
archaeological site type
An archaeological site type is a category used to classify locations of past human activity based on their physical characteristics, function, and cultural or temporal context.
-
C.
archaeological site network
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
-
D.
archaeological unit
An archaeological unit is a defined three-dimensional segment of an excavation area, recorded and analyzed as a discrete context of past human activity.
-
E.
archaeological site protection
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.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.