Triple
T24014142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carn Brea |
E594622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hillfort site |
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: hillfort site Context triple: [Carn Brea, instanceOf, hillfort site]
-
A.
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.
-
B.
archaeological mound
An archaeological mound is an artificial or modified natural elevation of earth, stone, or debris created by past human activity, often containing buried cultural materials and serving as a key source of information about ancient societies.
-
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.
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.
-
E.
Neolithic henge
A Neolithic henge is a prehistoric earthwork monument characterized by a circular or oval bank and internal ditch, often associated with ritual, ceremonial, or astronomical functions.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:41 p.m.