Triple
T28417803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osthryth of Northumbria |
E719857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon queen |
C54043
|
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 queen Context triple: [Osthryth of Northumbria, instanceOf, Anglo-Saxon queen]
-
A.
Anglo-Saxon royal princess
An Anglo-Saxon royal princess is a king’s daughter or close female relative in early medieval England, whose status embodies dynastic legitimacy, political alliance, and often religious patronage within the royal household.
-
B.
Anglo-Saxon monarch
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.
-
C.
Queen of England
The Queen of England is the female monarch who serves as the sovereign head of state of England (and, in modern times, the United Kingdom), embodying the continuity, authority, and ceremonial representation of the nation.
-
D.
Saxon princess
A Saxon princess is a noblewoman of royal Saxon lineage, typically characterized by her political significance in dynastic alliances, cultural influence within early medieval Germanic society, and role in consolidating power through marriage and patronage.
-
E.
12th-century English queen consort
A 12th-century English queen consort is the wife of an English king during the 1100s, serving as a political partner, dynastic link, and influential figure in courtly, diplomatic, and sometimes religious affairs.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:31 a.m.