Triple
T35935734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichtenau (Alluitsoq) mission area |
E1039299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian missionary settlement |
C33689
|
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 missionary settlement Context triple: [Lichtenau (Alluitsoq) mission area, instanceOf, Christian missionary settlement]
-
A.
Christian mission station
chosen
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.
-
B.
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.
-
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.
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.
-
E.
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.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.