Triple

T16931139
Position Surface form Disambiguated ID Type / Status
Subject Æthelberht II of East Anglia E410709 entity
Predicate instanceOf P0 FINISHED
Object East Anglian royal C6212 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: East Anglian royal
Context triple: [Æthelberht II of East Anglia, instanceOf, East Anglian royal]
  • A. Anglo-Saxon monarch chosen
    An Anglo-Saxon monarch is a hereditary or elected ruler who governed one of the early medieval English kingdoms prior to the Norman Conquest, wielding military, legal, and religious authority over their realm.
  • B. Anglo-Breton noble
    An Anglo-Breton noble is a medieval aristocrat of mixed English and Breton heritage who held land, titles, and political influence across both regions, often serving as a cultural and military intermediary between them.
  • C. Anglo-Norman dynasty
    The Anglo-Norman dynasty was the line of rulers of England, beginning with William the Conqueror after the 1066 Norman Conquest, who combined Norman, French, and Anglo-Saxon influences in medieval English governance and culture.
  • D. 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.
  • E. 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.
  • 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_69d886c886688190967be07322597ac9 completed April 10, 2026, 5:12 a.m.
Created at: April 10, 2026, 5:30 a.m.