Triple

T27884884
Position Surface form Disambiguated ID Type / Status
Subject Gododdin E705198 entity
Predicate instanceOf P0 FINISHED
Object early medieval Brittonic kingdom C53486 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: early medieval Brittonic kingdom
Context triple: [Gododdin, instanceOf, early medieval Brittonic kingdom]
  • A. 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.
  • B. Anglo-Saxon kingdom
    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.
  • C. medieval Welsh principality
    A medieval Welsh principality is a semi-independent territorial lordship in Wales, ruled by a native prince who exercised political, military, and legal authority within a feudal landscape dominated by competing Welsh dynasties and encroaching English power.
  • 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 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.
  • 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_69ef96b39c448190a9b3aa6672a5168f completed April 27, 2026, 5:02 p.m.
Created at: April 27, 2026, 6:32 p.m.