Triple
T32058364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaco Phenomenon |
E818679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric cultural phenomenon |
C34398
|
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 cultural phenomenon Context triple: [Chaco Phenomenon, instanceOf, prehistoric cultural phenomenon]
-
A.
prehistoric cultural landscape
A prehistoric cultural landscape is a geographic area where the physical environment and surviving traces of human activity together reflect the lifeways, beliefs, and land use practices of people who lived before written history.
-
B.
archaeological phenomenon
chosen
An archaeological phenomenon is a recurring pattern, feature, or assemblage identified in the archaeological record that reflects specific past human activities, behaviors, or cultural processes.
-
C.
prehistoric event
A prehistoric event is a significant occurrence or series of occurrences that took place before the advent of written records, known primarily through archaeological, geological, and paleontological evidence.
-
D.
prehistoric archaeological feature
A prehistoric archaeological feature is a non-portable physical trace of human activity, such as pits, ditches, postholes, or hearths, created before the advent of written records and preserved in the archaeological record.
-
E.
archaeological culture
An archaeological culture is a recurring assemblage of artifacts, features, and other material remains that archaeologists interpret as representing the activities and shared practices of a particular group of people in a specific time and place.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:21 a.m.