Triple
T18971148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godwin family |
E464171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon noble family |
C16850
|
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 noble family Context triple: [Godwin family, instanceOf, Anglo-Saxon noble family]
-
A.
medieval English noble dynasty
chosen
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
B.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
C.
House of Wessex member
A House of Wessex member is an individual belonging to the early medieval royal dynasty that ruled the Anglo-Saxon kingdom of Wessex and later much of England.
-
D.
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.
-
E.
Swedish noble family
A Swedish noble family is a lineage of individuals in Sweden historically granted hereditary noble status, often holding titles, estates, and social privileges recognized by the Swedish nobility system.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, noon