Triple
T14426613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markland |
E357713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viking Age toponym |
C22220
|
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: Viking Age toponym Context triple: [Markland, instanceOf, Viking Age toponym]
-
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 toponym
chosen
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.
-
C.
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.
-
D.
Norse settlement
A Norse settlement is a community established by Scandinavian peoples during the Viking Age and medieval period, typically featuring clustered farmsteads, longhouses, and associated agricultural or trading activities in regions they explored or colonized.
-
E.
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.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.