Triple
T18971149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godwin family |
E464171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval English dynasty |
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: medieval English dynasty Context triple: [Godwin family, instanceOf, medieval English dynasty]
-
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 French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
-
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.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
E.
British dynasty
A British dynasty is a succession of rulers or influential family members from the same lineage who hold power or prominence in Britain over multiple generations.
- 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