Triple
T30027488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raðulfr |
E762918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Norse personal name |
C17524
|
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 Norse personal name Context triple: [Raðulfr, instanceOf, Old Norse personal name]
-
A.
Old Norse name
chosen
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.
-
B.
Old Norse term
An Old Norse term is a word or expression originating from the Old Norse language, often preserved in historical texts, runic inscriptions, and modern scholarly or cultural usage.
-
C.
Old Norse toponym
An Old Norse toponym is a place name derived from the Old Norse language, often reflecting geographic features, settlement patterns, or cultural and religious practices of medieval Norse societies.
-
D.
Old High German personal name
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.
-
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.
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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:49 p.m.