Triple
T25675792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelcynda |
E643800
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site (uncertain location) |
C47908
|
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: archaeological site (uncertain location) Context triple: [Nelcynda, instanceOf, archaeological site (uncertain location)]
-
A.
archaeological locality
chosen
An archaeological locality is a specific geographic area where evidence of past human activity, such as artifacts, features, or structures, is found and studied in its environmental context.
-
B.
archaeological site type
An archaeological site type is a category used to classify locations of past human activity based on their physical characteristics, function, and cultural or temporal context.
-
C.
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.
-
D.
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.
-
E.
archaeological site record
An archaeological site record is a structured documentation of an archaeological location, detailing its features, artifacts, context, chronology, and research history for preservation and study.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:38 p.m.