Triple
T25639183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leof |
E642789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old English name element |
C34599
|
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 English name element Context triple: [Leof, instanceOf, Old English name element]
-
A.
Old English term
An Old English term is a word or expression originating from the early medieval English language (circa 5th–11th centuries), often preserved in historical texts and studied for its linguistic and cultural significance.
-
B.
Germanic name element
chosen
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.
-
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.
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.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:38 p.m.