Triple
T11390758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanctonbury Ring |
E269828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric hill fort |
C7612
|
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 hill fort Context triple: [Chanctonbury Ring, instanceOf, prehistoric hill fort]
-
A.
prehistoric platform mound
A prehistoric platform mound is a human-made earthen or stone elevation constructed in ancient times, typically serving as a base for structures, ceremonies, or elite residences within a broader cultural or ritual landscape.
-
B.
hill fort
chosen
A hill fort is a fortified settlement built on elevated ground, typically featuring defensive earthworks, walls, and ditches to control and protect the surrounding area.
-
C.
Iron Age site
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
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.
prehistoric mining site
A prehistoric mining site is an archaeological location where early human communities extracted raw materials such as stone, minerals, or metals using primitive tools and techniques before the advent of written records.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.