Triple
T14272283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran mission at Hermannsburg |
E353819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian mission station |
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 mission station Context triple: [Lutheran mission at Hermannsburg, instanceOf, Christian mission station]
-
A.
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.
-
B.
Christian mission hospital
A Christian mission hospital is a healthcare institution established and run on Christian principles that provides medical services while integrating spiritual care, evangelism, and community outreach, often in underserved or resource-limited areas.
-
C.
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.
-
D.
Catholic mission
A Catholic mission is a religious outpost or organized effort established by the Catholic Church to evangelize, provide pastoral care, and offer social services to a specific community or region.
-
E.
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.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.