Triple
T25119968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yácata |
E629238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological feature type |
C36994
|
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 feature type Context triple: [yácata, instanceOf, archaeological feature type]
-
A.
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.
-
B.
prehistoric archaeological feature
A prehistoric archaeological feature is a non-portable physical trace of human activity, such as pits, ditches, postholes, or hearths, created before the advent of written records and preserved in the archaeological record.
-
C.
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.
-
D.
archaeological component
An archaeological component is a distinct, temporally and functionally coherent set of artifacts, features, and other cultural materials at a site that represents a specific episode or phase of past human activity.
-
E.
archaeological mound
chosen
An archaeological mound is an artificial or modified natural elevation of earth, stone, or debris created by past human activity, often containing buried cultural materials and serving as a key source of information about ancient societies.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.