Triple
T36996822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon conquest of Wessex |
E915252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval event |
C13724
|
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 event Context triple: [Saxon conquest of Wessex, instanceOf, early medieval event]
-
A.
medieval event
chosen
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
B.
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.
-
C.
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.
-
D.
8th-century historical event
An 8th-century historical event is a significant occurrence between 700 and 799 CE that influenced the political, social, cultural, or religious development of societies during that period.
-
E.
medieval era
The medieval era is a historical period roughly spanning the 5th to the 15th century in Europe, characterized by feudal societies, the dominance of the Catholic Church, and the gradual emergence of towns, universities, and nation-states.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.