Triple
T11807110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taplow Barrow |
E280774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon burial mound |
C29853
|
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: Anglo-Saxon burial mound Context triple: [Taplow Barrow, instanceOf, Anglo-Saxon burial mound]
-
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.
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.
-
C.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
-
D.
Iron Age hoard
An Iron Age hoard is a deliberately buried collection of metal objects—such as tools, weapons, ornaments, and coins—from the Iron Age, often interpreted as ritual deposits, emergency storage, or wealth reserves.
-
E.
medieval motte
A medieval motte is a raised earthwork mound, often artificial, that served as the elevated foundation for a fortified structure such as a wooden or stone keep in early castles.
- F. None of above. chosen
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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.