Triple
T31644764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liddle Burnt Mound |
E807554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | burnt mound |
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: burnt mound Context triple: [Liddle Burnt Mound, instanceOf, burnt mound]
-
A.
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.
-
B.
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.
-
C.
Bronze Age cemetery
A Bronze Age cemetery is an archaeological burial ground dating to the Bronze Age, typically containing graves, tombs, or barrows with associated artifacts that reflect the social structure, rituals, and material culture of the period.
-
D.
Adena culture site
An Adena culture site is an archaeological location associated with the Adena people, characterized by burial mounds, earthworks, and related artifacts dating primarily from 1000 to 200 BCE in the Ohio Valley region.
-
E.
Kura–Araxes culture site
A Kura–Araxes culture site is an archaeological location associated with the Early Bronze Age Kura–Araxes cultural horizon, characterized by its distinctive pottery, architecture, and material remains across the South Caucasus and adjacent regions.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:50 p.m.