Triple
T6934939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Agustín culture (peripheral connections) |
E160530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peripheral archaeological manifestations |
C21368
|
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: peripheral archaeological manifestations Context triple: [San Agustín culture (peripheral connections), instanceOf, peripheral archaeological manifestations]
-
A.
archaeological discovery
An archaeological discovery is the unearthing or identification of physical remains, artifacts, or structures from past human activity that provide new insights into historical or prehistoric cultures and societies.
-
B.
archaeological excavation
An archaeological excavation is a systematic, carefully controlled process of uncovering, recording, and analyzing physical remains buried in the ground to reconstruct past human activities and cultures.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:27 p.m.