Triple
T10623477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent Mound |
E250262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric earthwork |
C26436
|
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 earthwork Context triple: [Serpent Mound, instanceOf, prehistoric earthwork]
-
A.
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.
-
B.
prehistoric underground burial complex
A prehistoric underground burial complex is a network of subterranean chambers and passages constructed by ancient societies to inter the dead, often accompanied by ritual artifacts and symbolic architecture.
-
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.
Hopewell culture earthwork
chosen
A Hopewell culture earthwork is a large, geometric or effigy-shaped earthen construction built by the Middle Woodland Hopewell peoples for ceremonial, social, and mortuary purposes in eastern North America.
-
E.
ancient village site
An ancient village site is an archaeological location preserving the remains of a past community’s dwellings, activity areas, and material culture, offering evidence of its social, economic, and environmental history.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 8:52 p.m.