Triple
T5891753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bornais Norse settlement |
E131005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viking Age settlement |
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 settlement Context triple: [Bornais Norse settlement, instanceOf, Viking Age settlement]
-
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.
Celtic settlement
A Celtic settlement is a community or habitation site established by Celtic peoples, typically characterized by fortified hilltops, roundhouses, and a material culture reflecting Celtic social, economic, and religious practices.
-
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.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
E.
historical settlement
A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political life.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.