Triple
T31843643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen Dinas hill |
E812874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age hillfort site |
C25917
|
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: Iron Age hillfort site Context triple: [Pen Dinas hill, instanceOf, Iron Age hillfort site]
-
A.
Iron Age site
chosen
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.
-
B.
Late Prehistoric archaeological site
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.
-
C.
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.
-
D.
Early Bronze Age site
An Early Bronze Age site is an archaeological location dating to the early phase of the Bronze Age, characterized by early metalworking, emerging social complexity, and associated settlement or burial remains.
-
E.
Roman-era site
A Roman-era site is a location containing physical remains, structures, or artifacts dating from the period of Roman rule, reflecting the architecture, infrastructure, and daily life of that time.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:50 p.m.