Triple
T13971835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oseberg ship burial |
E336083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viking Age ship burial |
C34437
|
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 ship burial Context triple: [Oseberg ship burial, instanceOf, Viking Age ship burial]
-
A.
Anglo-Saxon burial mound
An Anglo-Saxon burial mound is an earthen or stone-built barrow constructed in early medieval England to cover and mark the grave of an individual, often accompanied by grave goods and sometimes elaborate funerary structures.
-
B.
Iron Age hoard
An Iron Age hoard is a deliberately buried collection of metal objects—such as tools, weapons, ornaments, and coins—from the Iron Age, often interpreted as ritual deposits, emergency storage, or wealth reserves.
-
C.
Viking raid
A Viking raid is a swift, seaborne assault by Norse warriors on coastal or riverside settlements, aimed at plunder, captives, and territorial influence.
-
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.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.