Triple
T16726532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Communion mission priorities |
E406477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian mission strategy |
C37818
|
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: Christian mission strategy Context triple: [Anglican Communion mission priorities, instanceOf, Christian mission strategy]
-
A.
Christian missionary
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.
-
B.
Christian ministry
A Christian ministry is an organized effort or service, carried out by individuals or groups, dedicated to expressing and advancing the teachings, compassion, and mission of Jesus Christ in the world.
-
C.
Christian missionary journey
A Christian missionary journey is a purposeful trip undertaken by believers to share the Christian faith, serve communities, and support the growth of churches in various cultural or geographic contexts.
-
D.
Christian mission station
A Christian mission station is a settlement or compound established by missionaries to evangelize, provide religious instruction, and often offer education, medical care, and social services to a local community.
-
E.
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.
- F. None of above. chosen
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.