Triple
T27681353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamworth (de facto Mercian royal centre) |
E697916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon site |
C29712
|
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 site Context triple: [Tamworth (de facto Mercian royal centre), instanceOf, Anglo-Saxon site]
-
A.
Anglo-Saxon town
An Anglo-Saxon town is a small, early medieval English settlement characterized by wooden buildings, a central marketplace or meeting place, and a community structured around agriculture, trade, and local governance.
-
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.
early medieval site
chosen
An early medieval site is an archaeological location dating roughly from the 5th to the 11th century CE that preserves material evidence of social, political, economic, and religious life during the early Middle Ages.
-
D.
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.
-
E.
Anglo-Saxon institution
An Anglo-Saxon institution is a social, legal, political, or economic structure characteristic of early medieval England and related Germanic societies, shaped by their customs, governance practices, and cultural norms.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:47 p.m.