Triple
T20397232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talbot |
E500239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman-language surname |
C9103
|
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-language surname Context triple: [Talbot, instanceOf, Norman-language surname]
-
A.
Gaelic-language surname
A Gaelic-language surname is a family name originating from the Gaelic languages (such as Irish or Scottish Gaelic), typically reflecting ancestral lineage, occupation, or geographic origin through traditional Gaelic naming conventions.
-
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.
Welsh-language surname
A Welsh-language surname is a family name originating from Wales that is derived from or expressed in the Welsh language, often reflecting patronymic traditions, geographic features, or personal characteristics.
-
D.
English-language family name
An English-language family name is a hereditary surname originating from English-speaking cultures, often derived from occupations, locations, personal characteristics, or ancestral given names.
-
E.
French-language surname
chosen
A French-language surname is a family name originating from or adapted to the French language, often reflecting geographic, occupational, descriptive, or patronymic roots within Francophone cultures.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.