Triple
T11649897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubrey holes |
E276874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric archaeological feature |
C29584
|
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: prehistoric archaeological feature Context triple: [Aubrey holes, instanceOf, prehistoric archaeological feature]
-
A.
prehistoric platform mound
A prehistoric platform mound is a human-made earthen or stone elevation constructed in ancient times, typically serving as a base for structures, ceremonies, or elite residences within a broader cultural or ritual landscape.
-
B.
prehistoric mining site
A prehistoric mining site is an archaeological location where early human communities extracted raw materials such as stone, minerals, or metals using primitive tools and techniques before the advent of written records.
-
C.
Iron Age site
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
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.
prehistoric trackway
A prehistoric trackway is a preserved sequence of fossilized footprints or impressions left by ancient organisms, providing evidence of their movement, behavior, and environment.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.