Triple
T6254704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birka and Hovgården |
E140133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viking Age site |
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: Viking Age site Context triple: [Birka and Hovgården, instanceOf, Viking Age site]
-
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.
prehistoric mining site
A prehistoric mining site is an archaeological location where early human communities extracted raw materials such as stone, minerals, or metals using primitive tools and techniques before the advent of written records.
-
C.
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.
-
D.
maritime archaeological site
A maritime archaeological site is a submerged or coastal location containing physical remains, artifacts, or environmental evidence that reveal past human activities related to seafaring, trade, or coastal life.
-
E.
reconstructed historic site
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:24 p.m.