Triple
T31950417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Peninsula complex |
E815763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | precontact Indigenous culture |
C27190
|
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: precontact Indigenous culture Context triple: [Point Peninsula complex, instanceOf, precontact Indigenous culture]
-
A.
Pre-Columbian culture
chosen
Pre-Columbian culture encompasses the diverse societies, traditions, technologies, and belief systems that existed throughout the Americas before the arrival of Christopher Columbus and subsequent European contact.
-
B.
pre-Columbian cultural period
A pre-Columbian cultural period is a span of time in the Americas before European contact, characterized by distinct indigenous societies, technologies, and belief systems.
-
C.
Paleoindian cultural tradition
A Paleoindian cultural tradition is an archaeological classification for the earliest known Indigenous peoples in the Americas, characterized by distinctive stone tool technologies, mobile hunter-gatherer lifeways, and adaptation to late Pleistocene environments.
-
D.
indigenous cultural landscape
An indigenous cultural landscape is a geographic area shaped by the long-term, reciprocal relationships between Indigenous peoples and their environment, reflecting their cultural practices, knowledge systems, and spiritual values.
-
E.
pre-Columbian cultural area
A pre-Columbian cultural area is a geographically defined region of the Americas characterized by shared cultural, social, and technological traits among Indigenous societies prior to European contact.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:07 a.m.