Triple
T5987435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermín Francisco de Lasuén |
E133262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Catholic missionary |
C4952
|
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: Roman Catholic missionary Context triple: [Fermín Francisco de Lasuén, instanceOf, Roman Catholic missionary]
-
A.
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.
-
B.
Roman Catholic mission network
A Roman Catholic mission network is an organized system of churches, religious orders, and agencies that coordinate evangelization, pastoral care, education, and charitable works to spread and sustain the Catholic faith across different regions and cultures.
-
C.
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.
-
D.
Dominican priest
A Dominican priest is a Catholic cleric belonging to the Order of Preachers (Dominicans), dedicated to preaching, teaching, and theological study in the service of the Church.
-
E.
Christian missionary
chosen
A Christian missionary is an individual who is sent, often by a church or religious organization, to spread the Christian faith and provide spiritual, educational, or humanitarian support in various cultural or geographic contexts.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.