Triple
T21467208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harper |
E529622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | surname of Anglo-Saxon origin |
C44812
|
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: surname of Anglo-Saxon origin Context triple: [Harper, instanceOf, surname of Anglo-Saxon origin]
-
A.
surname of German origin
A surname of German origin is a family name derived from the German language and cultural or geographic roots within German-speaking regions.
-
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.
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.
-
D.
hypothesized Old English personal name
A hypothesized Old English personal name is a reconstructed or inferred individual name from the Old English period that lacks direct attestation in surviving historical records but is proposed based on linguistic and onomastic evidence.
-
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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:14 p.m.