Triple
T21711266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Muhlenberg |
E535911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patriarch of German-American Lutheranism |
C7217
|
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: patriarch of German-American Lutheranism Context triple: [Henry Muhlenberg, instanceOf, patriarch of German-American Lutheranism]
-
A.
German Lutheran
A German Lutheran is an adherent of the Lutheran branch of Protestant Christianity whose religious identity and practices are shaped by the theological heritage of Martin Luther within the cultural and historical context of Germany.
-
B.
Lutheran minister
chosen
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.
-
C.
German bishop
A German bishop is a high-ranking clergy member of the Christian church in Germany, responsible for overseeing a diocese’s spiritual leadership, administration, and representation within both ecclesiastical and public spheres.
-
D.
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.
-
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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:46 p.m.