Triple
T31494117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Presiding Bishop of the Evangelical Lutheran Church in America |
E803488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church executive office |
C6232
|
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: church executive office Context triple: [Office of the Presiding Bishop of the Evangelical Lutheran Church in America, instanceOf, church executive office]
-
A.
religious leadership office
chosen
A religious leadership office is an organizational unit or position within a faith community responsible for guiding spiritual practice, administering religious functions, and overseeing the governance and pastoral care of its members.
-
B.
head of church
The head of church is the highest-ranking religious leader who holds ultimate spiritual authority and administrative responsibility over a particular Christian church or denomination.
-
C.
archiepiscopal office
An archiepiscopal office is the official position, authority, and administrative center associated with an archbishop’s leadership over an archdiocese and its ecclesiastical affairs.
-
D.
Lutheran church office
A Lutheran church office is the administrative center of a Lutheran congregation where pastoral staff and lay workers coordinate worship, ministries, records, and daily church operations.
-
E.
church organization
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:40 p.m.