Triple
T35672205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyne Valley Neolithic cemetery |
E1030749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Neolithic cemetery |
C42718
|
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: Neolithic cemetery Context triple: [Boyne Valley Neolithic cemetery, instanceOf, Neolithic cemetery]
-
A.
Bronze Age cemetery
A Bronze Age cemetery is an archaeological burial ground dating to the Bronze Age, typically containing graves, tombs, or barrows with associated artifacts that reflect the social structure, rituals, and material culture of the period.
-
B.
neolithic site
chosen
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.
-
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.
Scythian-era burial ground
A Scythian-era burial ground is an archaeological site containing kurgans (burial mounds) and associated grave goods that reflect the funerary practices, social hierarchy, and nomadic culture of the Scythian peoples.
-
E.
Anglo-Saxon burial mound
An Anglo-Saxon burial mound is an earthen or stone-built barrow constructed in early medieval England to cover and mark the grave of an individual, often accompanied by grave goods and sometimes elaborate funerary structures.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.