Triple
T11629053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubian monuments |
E276348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site collection |
C30791
|
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 collection Context triple: [Nubian monuments, instanceOf, archaeological site collection]
-
A.
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.
-
B.
archaeological artifact collection
An archaeological artifact collection is an organized assemblage of material remains from past human activities, systematically gathered, documented, and preserved for research, interpretation, and education.
-
C.
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.
-
D.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.