Triple
T2448532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Watch Tower Bible and Tract Society |
E53648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious organization 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: religious organization office Context triple: [President of the Watch Tower Bible and Tract Society, instanceOf, religious organization 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.
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.
-
C.
religious nonprofit
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.
-
D.
religious network
A religious network is a structured system of individuals, groups, and institutions connected by shared beliefs, practices, and organizational ties that facilitate the spread and maintenance of a religious tradition.
-
E.
religious structure
A religious structure is a building or space specifically designed and used for worship, rituals, and other activities associated with a particular faith or spiritual tradition.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.