Triple
T14272284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran mission at Hermannsburg |
E353819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran mission |
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: Lutheran mission Context triple: [Lutheran mission at Hermannsburg, instanceOf, Lutheran mission]
-
A.
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.
-
B.
Lutheran church
A Lutheran church is a Christian congregation or building that follows the teachings of Martin Luther and the Lutheran Confessions, emphasizing salvation by grace through faith, the authority of Scripture, and liturgical worship.
-
C.
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.
-
D.
Russian Orthodox Church mission
A Russian Orthodox Church mission is a religious organization or outpost established to spread the Orthodox faith, provide pastoral care, and support spiritual, cultural, and charitable activities among local or diaspora communities under the jurisdiction of the Russian Orthodox Church.
-
E.
Lutheran diocese
A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.