Triple
T25617733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | witenagemot |
E642203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval English council |
C42587
|
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 English council Context triple: [witenagemot, instanceOf, early medieval English council]
-
A.
medieval parliament
A medieval parliament is an assembly of nobles, clergy, and sometimes commoners convened by a monarch to advise on governance, consent to taxation, and address matters of law and policy.
-
B.
early medieval English person
An early medieval English person is an individual who lived in England roughly between the 5th and 11th centuries, shaped by a mix of Anglo-Saxon, Viking, and early Christian cultural, social, and political influences.
-
C.
medieval political agreement
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
-
D.
Anglo-Saxon institution
chosen
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.
-
E.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:01 p.m.