Triple
T27964579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magonsæte |
E704680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon sub-kingdom |
C8302
|
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 sub-kingdom Context triple: [Magonsæte, instanceOf, Anglo-Saxon sub-kingdom]
-
A.
Anglo-Saxon kingdom
chosen
An Anglo-Saxon kingdom is a political entity established in early medieval England by Germanic peoples, characterized by its own monarchy, territorial domain, legal customs, and social hierarchy prior to the Norman Conquest.
-
B.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
C.
Anglo-Saxon
Anglo-Saxon refers to the early medieval Germanic peoples from present-day Germany and Denmark who settled in England from the 5th century onward, as well as their language, culture, and societal structures.
-
D.
Pictish kingdom
The Pictish kingdom was an early medieval confederation of tribal societies in what is now northern and eastern Scotland, known for its distinctive symbol stones, warrior culture, and eventual unification with the Gaelic Scots.
-
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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 7:34 p.m.