Triple
T11365752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Board for Presbyterian Foreign Missions |
E269200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Presbyterian missionary agency |
C19115
|
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: Presbyterian missionary agency Context triple: [Independent Board for Presbyterian Foreign Missions, instanceOf, Presbyterian missionary agency]
-
A.
Presbyterian missionary
A Presbyterian missionary is a Christian emissary affiliated with the Presbyterian tradition who is sent to spread the faith, establish churches, and provide spiritual and social services in local or foreign communities.
-
B.
missionary society
chosen
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.
Seventh-day Adventist mission station
A Seventh-day Adventist mission station is a religious outpost established by the Seventh-day Adventist Church to evangelize, provide education and healthcare, and support community development in a specific region.
-
D.
Methodist organization
A Methodist organization is a structured group or institution that operates according to Methodist Christian beliefs, practices, and governance to support worship, ministry, and community service.
-
E.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.