Triple
T30743572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madisonville site |
E782756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric village site |
C57202
|
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 village site Context triple: [Madisonville site, instanceOf, prehistoric village site]
-
A.
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.
-
B.
neolithic site
A neolithic site is an archaeological location containing material remains and features from the New Stone Age, reflecting early farming communities, permanent settlements, and the development of complex social and technological practices.
-
C.
Late Prehistoric archaeological site
chosen
A Late Prehistoric archaeological site is a location containing material remains and features dating to the final phases of prehistory, just before or during early contact with historically documented societies, which reveal patterns of subsistence, technology, and social organization.
-
D.
mesolithic site
A mesolithic site is an archaeological location containing evidence of human activity from the Mesolithic period, typically characterized by microlithic stone tools and transitional hunter-gatherer lifeways between the Paleolithic and Neolithic eras.
-
E.
megalithic site
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:38 p.m.