Triple
T6328171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green |
E141909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon surname |
C13300
|
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-Saxon surname Context triple: [Green, instanceOf, Anglo-Saxon surname]
-
A.
Old English toponym
An Old English toponym is a place-name whose form and meaning originate from the Old English language, often reflecting early medieval landscape features, settlements, or ownership.
-
B.
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.
-
C.
English-language family name
chosen
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.
-
D.
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.
-
E.
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.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.