Triple
T22511946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transalpine Saxons |
E556541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval ethnic group |
C6355
|
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: early medieval ethnic group Context triple: [Transalpine Saxons, instanceOf, early medieval ethnic group]
-
A.
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.
-
B.
Germanic tribe
chosen
A Germanic tribe is a social and political group of early Germanic-speaking peoples, typically organized around kinship, warrior culture, and shared customs in ancient and early medieval Europe.
-
C.
early medieval period
The early medieval period is a historical era roughly spanning the 5th to the 10th centuries CE, marked by the transformation of the Roman world, the formation of new kingdoms, the spread of Christianity and Islam, and the gradual development of medieval European, Byzantine, and Islamic civilizations.
-
D.
Celtic-Germanic tribe
A Celtic-Germanic tribe is a historically mixed or transitional ethnic group that exhibits cultural, linguistic, and social characteristics derived from both Celtic and Germanic peoples.
-
E.
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.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.