Triple
T29772363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Methodist clergy |
E755283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office in the United Methodist Church |
C55686
|
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: office in the United Methodist Church Context triple: [United Methodist clergy, instanceOf, office in the United Methodist Church]
-
A.
Methodist organization
A Methodist organization is a structured group or institution that operates according to Methodist Christian beliefs, practices, and governance to support worship, ministry, and community service.
-
B.
United Methodist bishop
A United Methodist bishop is an ordained clergy leader elected to oversee and guide the spiritual, administrative, and missional life of one or more regional conferences within the United Methodist Church.
-
C.
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.
-
D.
United Methodist Church publication
A United Methodist Church publication is an official or affiliated printed or digital resource that communicates the denomination’s theology, news, teachings, and guidance to its members and the wider public.
-
E.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:43 p.m.