Triple
T4669344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hantescire |
E102923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old English toponym |
C16156
|
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 toponym Context triple: [Hantescire, instanceOf, Old English toponym]
-
A.
Anglo-Saxon
Anglo-Saxon refers to the early medieval Germanic peoples from present-day Germany and Denmark who settled in England from the 5th century onward, as well as their language, culture, and societal structures.
-
B.
Latin toponym
A Latin toponym is a place name expressed in the Latin language, often used historically in maps, texts, and scholarly works to refer to geographic locations.
-
C.
Gaelic linguistic element
A Gaelic linguistic element is a fundamental unit of the Gaelic language—such as a sound, word, or grammatical structure—that contributes to meaning and expression within Scottish or Irish Gaelic.
-
D.
Anglo-Saxon kingdom
An Anglo-Saxon kingdom is a political entity established in early medieval England by Germanic peoples, characterized by its own monarchy, territorial domain, legal customs, and social hierarchy prior to the Norman Conquest.
-
E.
medieval North Germanic language variety
A medieval North Germanic language variety is a historical form of a Scandinavian language spoken in Northern Europe during the Middle Ages, characterized by its distinct phonology, morphology, and vocabulary relative to both earlier Norse and later modern Scandinavian languages.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.