Triple
T18825349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monulphus of Maastricht |
E460370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval person |
C3415
|
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 person Context triple: [Monulphus of Maastricht, instanceOf, early medieval person]
-
A.
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.
-
B.
8th-century person
An 8th-century person is an individual who lived during the years 700–799 CE, shaped by the political, cultural, and technological contexts of that era.
-
C.
7th-century person
A 7th-century person is an individual who lived during the years 600–699 CE, shaped by the political, religious, and cultural transformations characteristic of that century.
-
D.
medieval people
chosen
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
E.
8th-century English person
An 8th-century English person is an inhabitant of the various Anglo-Saxon kingdoms in England during the 700s, living within a predominantly agrarian, Christianizing society shaped by emerging political consolidation and monastic culture.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.