Triple
T17388610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hruodperht |
E422755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old High German personal 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: Old High German personal name Context triple: [Hruodperht, instanceOf, Old High German personal name]
-
A.
Old High German poem
An Old High German poem is a verse composition written in the Old High German language (c. 750–1050 CE), typically preserved in medieval manuscripts and reflecting early Germanic culture, Christianization, and poetic traditions.
-
B.
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.
-
C.
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.
-
D.
German-language given name and surname combination
A German-language given name and surname combination is a full personal name constructed from a first name and a family name that both originate from or are commonly used in German-speaking regions.
-
E.
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.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.