Triple
T8317598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Montgomery |
E194744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman noble family |
C811
|
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: Norman noble family Context triple: [de Montgomery, instanceOf, Norman noble 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.
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.
-
C.
Scottish noble family branch
A Scottish noble family branch is a cadet line descending from a principal aristocratic house in Scotland, holding its own titles, lands, and heraldic distinctions while remaining part of the wider clan or lineage.
-
D.
Norman ruler
A Norman ruler is a sovereign or feudal lord of Norman origin who exercises political and military authority over a territory, often characterized by a blend of Viking heritage and Frankish culture.
-
E.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:55 p.m.