Triple
T17611466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mission of Saint Liudger |
E428975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval religious mission |
C35752
|
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 religious mission Context triple: [mission of Saint Liudger, instanceOf, early medieval religious mission]
-
A.
religious mission
chosen
A religious mission is an organized effort by a faith community or institution to spread its beliefs, provide spiritual guidance, and often deliver social or humanitarian services to people beyond its existing membership.
-
B.
Catholic mission
A Catholic mission is a religious outpost or organized effort established by the Catholic Church to evangelize, provide pastoral care, and offer social services to a specific community or region.
-
C.
early medieval religious text
An early medieval religious text is a written work produced roughly between the 5th and 11th centuries that conveys, interprets, or codifies spiritual beliefs, practices, or doctrines within a particular religious tradition.
-
D.
Gregorian missionary
A Gregorian missionary is a Christian evangelist associated with the Gregorian Reform era who travels to spread the faith, promote church discipline, and extend papal influence in accordance with Gregorian principles.
-
E.
Anglo-Saxon missionary
An Anglo-Saxon missionary is a Christian evangelist from early medieval England who traveled to foreign regions, particularly continental Europe, to convert local populations and establish or strengthen the Church.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.