Triple

T15738191
Position Surface form Disambiguated ID Type / Status
Subject Gardar ruins E381530 entity
Predicate instanceOf P0 FINISHED
Object Norse ruins C12118 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: Norse ruins
Context triple: [Gardar ruins, instanceOf, Norse ruins]
  • A. Norse settlement chosen
    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.
  • B. Viking Age grave
    A Viking Age grave is an archaeological burial site from roughly the late 8th to early 11th centuries, typically containing human remains along with grave goods such as weapons, jewelry, tools, and sometimes boats, reflecting Norse social status, beliefs, and funerary practices.
  • C. Viking Age ship burial
    A Viking Age ship burial is a funerary practice in which an individual, often of high status, was interred within a ship or boat along with grave goods, symbolizing their journey to the afterlife and reflecting their social and maritime significance.
  • D. 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.
  • E. Dwarven kingdom
    A Dwarven kingdom is a subterranean, clan-based realm of stout, industrious dwarves renowned for their masterful craftsmanship, rich mineral wealth, and fiercely defended stone fortresses.
  • 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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:46 a.m.