Triple
T21432901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Melchior Muhlenberg |
E528733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founder of Lutheran Church in America |
C13287
|
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: founder of Lutheran Church in America Context triple: [Henry Melchior Muhlenberg, instanceOf, founder of Lutheran Church in America]
-
A.
Lutheran minister
A Lutheran minister is an ordained clergy member in the Lutheran tradition who leads worship, preaches, administers sacraments, and provides spiritual care and guidance to a congregation.
-
B.
Lutheran publisher
A Lutheran publisher is an organization that produces, distributes, and promotes books, periodicals, and other media that reflect and support Lutheran theology, worship, education, and devotional life.
-
C.
Swedish Lutheran archbishop
A Swedish Lutheran archbishop is the highest-ranking bishop within the Church of Sweden, responsible for providing spiritual leadership, overseeing church doctrine and administration, and representing the national Lutheran church in both religious and public affairs.
-
D.
founder of religious organization
chosen
A founder of a religious organization is an individual who originates, establishes, and provides the initial doctrine, structure, and leadership for a new religious movement or institution.
-
E.
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.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:54 p.m.