Triple
T15049796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Walpurga |
E379329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 8th-century Christian |
C28865
|
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: 8th-century Christian Context triple: [Saint Walpurga, instanceOf, 8th-century Christian]
-
A.
6th-century Christian clergy
6th-century Christian clergy were ordained religious leaders who administered sacraments, guided spiritual life, and often wielded significant social and political influence within the early medieval Christian Church.
-
B.
2nd-century Christian
A 2nd-century Christian is a follower of Jesus within the diverse and developing early Church of the 100s CE, navigating emerging doctrines, sporadic persecution, and the transition from apostolic tradition to organized theology and community life.
-
C.
early medieval Christian text
An early medieval Christian text is a written work produced roughly between the 5th and 11th centuries that reflects and shapes Christian theology, liturgy, devotion, or ecclesiastical practice within the cultural and political contexts of early medieval Europe and the Mediterranean.
-
D.
8th-century person
chosen
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.
-
E.
Late Antique Christian
A Late Antique Christian is an adherent of Christianity living between roughly the 3rd and 8th centuries CE, shaped by the Roman Empire’s transformation, emerging Christian institutions, and evolving theological and cultural debates.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.