Triple
T26152941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Venn (Secretary of the Church Missionary Society) |
E659876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | missionary strategist |
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: missionary strategist Context triple: [Henry Venn (Secretary of the Church Missionary Society), instanceOf, missionary strategist]
-
A.
missionary directive
A missionary directive is an authoritative instruction or set of guidelines that defines the goals, methods, and ethical boundaries for individuals or groups engaged in religious outreach or proselytizing activities.
-
B.
missionary society
A missionary society is an organized religious group dedicated to planning, supporting, and carrying out missionary work, often including evangelism, education, and social services in domestic or foreign fields.
-
C.
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.
-
D.
Christian mission strategy
Christian mission strategy is the intentional planning and implementation of biblically grounded, culturally sensitive methods to communicate the gospel, make disciples, and establish sustainable Christian communities in specific contexts.
-
E.
mission church
A mission church is a religious building or congregation established by a parent church or missionary organization to serve a specific community, often in a developing or newly evangelized area.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
Created at: April 26, 2026, 8:26 p.m.