Triple
T21772483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Castle Mound |
E537469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | castle mound |
C33571
|
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: castle mound Context triple: [Bedford Castle Mound, instanceOf, castle mound]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
castle remains
chosen
Castle remains are the surviving structural fragments and archaeological traces of a once-complete castle, such as ruined walls, foundations, towers, and earthworks, that reveal its former layout and historical use.
-
E.
hill fort
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.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.