Triple
T26041565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roet |
E647704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval English 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: medieval English family Context triple: [Roet, instanceOf, medieval English 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 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.
-
C.
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.
-
D.
medieval English name
A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
-
E.
medieval English noblewoman
A medieval English noblewoman is an aristocratic woman of high social rank in England’s Middle Ages, whose life centers on managing estates, forging political alliances through marriage, and upholding the social, cultural, and religious expectations of the nobility.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:08 a.m.