Triple
T9253079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etowah Indian Mounds |
E222373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric earthwork complex |
C10580
|
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 complex Context triple: [Etowah Indian Mounds, instanceOf, prehistoric earthwork complex]
-
A.
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.
-
B.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
C.
monumental complex
chosen
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
D.
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.
-
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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:31 p.m.