Triple
T24080394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langham Literature |
E596486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian ministry initiative |
C7156
|
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 ministry initiative Context triple: [Langham Literature, instanceOf, Christian ministry initiative]
-
A.
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.
-
B.
Christian community organization
A Christian community organization is a faith-based group that organizes and supports religious, social, and charitable activities to serve and spiritually nurture its local community.
-
C.
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.
-
D.
evangelical organization
chosen
An evangelical organization is a Christian group or institution dedicated to spreading the gospel, fostering personal faith in Jesus Christ, and promoting biblical teachings through worship, outreach, and service.
-
E.
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.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:43 p.m.