Triple
T26423057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking York |
E664292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Scandinavian town |
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: Anglo-Scandinavian town Context triple: [Viking York, instanceOf, Anglo-Scandinavian town]
-
A.
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.
-
B.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
C.
former Hanseatic town
A former Hanseatic town is a city that was once a member of the medieval Hanseatic League, historically engaged in extensive maritime trade and governed by shared commercial and legal frameworks.
-
D.
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.
-
E.
Renaissance town
A Renaissance town is an urban settlement characterized by humanist-inspired planning, harmonious proportions, and architecture that blends classical forms with emerging civic, commercial, and cultural functions of the 14th–17th centuries.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:44 p.m.