Triple
T30046807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Thibouville |
E763476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Norman aristocratic family |
C27116
|
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 Norman aristocratic family Context triple: [de Thibouville, instanceOf, medieval Norman aristocratic family]
-
A.
medieval English noble dynasty
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.
member of the Norman nobility
A member of the Norman nobility is an individual belonging to the hereditary warrior-aristocratic elite of Norman society, holding land, titles, and political influence derived from feudal bonds and conquest.
-
C.
medieval ruling family
chosen
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.
-
D.
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.
-
E.
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.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:54 p.m.