Triple
T29772706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Methodist Communications |
E755290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church communications agency |
C17722
|
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 communications agency Context triple: [United Methodist Communications, instanceOf, church communications agency]
-
A.
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.
-
B.
religious media organization
chosen
A religious media organization is an entity that produces, curates, and distributes content across various media platforms to promote, explain, or support specific religious beliefs, practices, or communities.
-
C.
mission church
A mission church is a religious building or congregation established by a parent church or missionary organization to serve a specific community, often in a developing or newly evangelized area.
-
D.
religious organization committee
A religious organization committee is a structured group within a faith-based institution responsible for planning, coordinating, and overseeing specific religious, administrative, or community activities in alignment with the organization’s beliefs and goals.
-
E.
communications agency
A communications agency is a professional service firm that develops and executes strategic messaging, branding, and media outreach to help organizations effectively engage and influence their target audiences.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:43 p.m.