Triple
T22205398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religious Support Office |
E548792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious support organization |
C9456
|
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: religious support organization Context triple: [Religious Support Office, instanceOf, religious support organization]
-
A.
religious nonprofit
chosen
A religious nonprofit is an organization formed primarily to advance, support, or practice a particular faith or set of spiritual beliefs, operating on a not-for-profit basis and typically funded through donations, grants, and volunteer efforts.
-
B.
religious umbrella organization
A religious umbrella organization is a coordinating body that unites and represents multiple related religious groups, denominations, or institutions under a common framework for shared governance, advocacy, and collaboration.
-
C.
religious corporation
A religious corporation is a legally recognized organization formed to own property, manage finances, and conduct activities on behalf of a religious group or institution.
-
D.
faith-based organizations
Faith-based organizations are groups or institutions whose missions, activities, and community services are primarily guided by shared religious beliefs and spiritual values.
-
E.
religious organization board
A religious organization board is a governing body of appointed or elected individuals responsible for overseeing the spiritual, administrative, financial, and strategic direction of a faith-based institution.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.