Triple
T26768361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Burca |
E675008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman-origin 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: Norman-origin surname Context triple: [de Burca, instanceOf, Norman-origin surname]
-
A.
Anglo-Norman surname
chosen
An Anglo-Norman surname is a family name of Norman French origin that became established in England and surrounding regions following the Norman Conquest, often reflecting Norman personal names, occupations, or places.
-
B.
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.
-
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.
Scottish surname
A Scottish surname is a family name originating from Scotland, often derived from Gaelic, Norse, or Anglo-Norman roots and reflecting ancestral occupations, locations, or clan affiliations.
-
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.
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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 4:01 a.m.