Triple
T3235754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Odoacer |
E67851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Germanic-ruled kingdom |
C7995
|
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: Germanic-ruled kingdom Context triple: [Kingdom of Odoacer, instanceOf, Germanic-ruled kingdom]
-
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.
Germanic ruler
A Germanic ruler is a sovereign or chieftain from one of the Germanic peoples who exercised political, military, and often religious authority over a tribe, kingdom, or territory in Europe.
-
C.
Germanic tribe
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.
-
D.
early medieval kingdom
chosen
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.
Anglo-Saxon monarch
An Anglo-Saxon monarch is a hereditary or elected ruler who governed one of the early medieval English kingdoms prior to the Norman Conquest, wielding military, legal, and religious authority over their realm.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:08 p.m.