Triple
T24061830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wido |
E595974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Germanic given name |
C38517
|
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: medieval Germanic given name Context triple: [Wido, instanceOf, medieval Germanic given name]
-
A.
Germanic name element
A Germanic name element is a meaningful component, often a root or morpheme, derived from Germanic languages that combines with others to form personal names conveying specific attributes, roles, or qualities.
-
B.
Old High German personal name
chosen
An Old High German personal name is a given name used by German-speaking peoples between roughly the 6th and 11th centuries, typically formed from meaningful Germanic word elements reflecting traits, virtues, or social roles.
-
C.
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.
-
D.
Old Norse name
An Old Norse name is a personal name originating from the Old Norse language and culture, often composed of meaningful elements reflecting attributes, deities, or aspects of Viking Age society.
-
E.
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.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:38 p.m.