Triple
T15020901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emeryville Shellmound |
E378080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shellmound |
C29165
|
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: shellmound Context triple: [Emeryville Shellmound, instanceOf, shellmound]
-
A.
prehistoric platform mound
chosen
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.
Mississippian culture center
A Mississippian culture center is a facility or site dedicated to preserving, interpreting, and educating the public about the Mississippian Native American civilization, its mound-building traditions, and its social, political, and religious practices.
-
C.
Hopewell culture earthwork
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.
-
D.
megalithic jar site
A megalithic jar site is an archaeological landscape characterized by the presence of large, carved stone jars, often arranged in groups, whose original function is typically associated with ancient ritual, funerary, or storage practices.
-
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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:56 a.m.