Triple
T30743527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SunWatch Indian Village |
E782755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed prehistoric village |
C8110
|
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: reconstructed prehistoric village Context triple: [SunWatch Indian Village, instanceOf, reconstructed prehistoric village]
-
A.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
B.
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.
-
C.
restored village
A restored village is a historically significant settlement that has been carefully renovated or reconstructed to reflect its original appearance, architecture, and way of life, often for educational, cultural, or tourism purposes.
-
D.
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.
-
E.
cultural village
A cultural village is a community or attraction designed to preserve, showcase, and educate visitors about the traditional lifestyles, customs, architecture, and arts of a particular culture or ethnic group.
- 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.