Triple
T4354487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moundville Archaeological Park |
E98112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric Native American site |
C12166
|
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 Native American site Context triple: [Moundville Archaeological Park, instanceOf, prehistoric Native American site]
-
A.
pre-Columbian site
chosen
A pre-Columbian site is an archaeological location in the Americas that preserves evidence of human activity and cultures that existed before the arrival of Christopher Columbus in 1492.
-
B.
paleoanthropological site
A paleoanthropological site is a location where physical evidence of ancient humans and their ancestors—such as fossils, artifacts, and environmental remains—is preserved and studied to understand human evolution.
-
C.
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.
-
D.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
E.
Olmec site
An Olmec site is an archaeological location associated with the Olmec civilization, characterized by monumental stone sculptures, ceremonial centers, and evidence of early Mesoamerican cultural development.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:15 p.m.