Triple
T26339735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FitzRobert |
E662612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Norman surname |
C51434
|
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-Norman surname Context triple: [FitzRobert, instanceOf, Anglo-Norman surname]
-
A.
surname of Anglo-Saxon origin
A surname of Anglo-Saxon origin is a family name derived from the Old English language and early medieval English culture, often based on occupations, locations, personal characteristics, or patronymic forms.
-
B.
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.
-
C.
clan of Norman origin
A clan of Norman origin is a kinship group or lineage whose ancestry traces back to the Normans, often characterized by shared surnames, heraldry, and historical ties to Norman conquests and settlements.
-
D.
Breton family name
A Breton family name is a hereditary surname originating from the Brittany region of France, often reflecting Breton language, geography, occupations, or lineage.
-
E.
Cornish surname
A Cornish surname is a family name originating from Cornwall, England, often derived from Cornish language words, local place names, occupations, or descriptive nicknames unique to Cornish heritage.
- F. None of above. chosen
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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:38 p.m.