Triple
T16581336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botolph |
E402837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old English given name |
C27576
|
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 given name Context triple: [Botolph, instanceOf, Old English given 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.
medieval English name
chosen
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.
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.
hypothesized Old English tribal or patronymic name
A hypothesized Old English tribal or patronymic name is a reconstructed personal or group designation inferred from linguistic, historical, or onomastic evidence, believed to have identified a kin group or descendants of a common ancestor in early medieval England.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.