Triple
T8312715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wæcel |
E194629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hypothesized Old English personal name |
C24212
|
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: hypothesized Old English personal name Context triple: [Wæcel, instanceOf, hypothesized Old English personal name]
-
A.
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.
-
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.
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.
medieval Latin name
A medieval Latin name is a personal or place designation used in the Middle Ages, typically rendered in Latinized form to align with ecclesiastical, scholarly, or administrative conventions of the period.
-
E.
Gaelic name
A Gaelic name is a personal or place name originating from the Gaelic languages (Irish, Scottish, or Manx), typically reflecting Celtic linguistic forms, cultural heritage, and traditional naming patterns.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.