Triple
T18671746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bretwalda |
E456492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon political concept |
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 political concept Context triple: [Bretwalda, instanceOf, Anglo-Saxon political concept]
-
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.
Anglo-American political tradition
The Anglo-American political tradition is a lineage of political thought and institutions rooted in English common law, parliamentary government, and liberal constitutionalism that has shaped the democratic practices of Britain, the United States, and related societies.
-
C.
ancient Indian political concept
An ancient Indian political concept refers to the traditional ideas, institutions, and theories of governance, statecraft, and power articulated in classical Indian texts and practices, such as those found in the Arthashastra and Dharmashastra.
-
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-Saxonist
An Anglo-Saxonist is a scholar or specialist who studies the language, literature, history, and culture of early medieval England, particularly the Old English (Anglo-Saxon) period.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.