Triple
T6894817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Translation Services of Jehovah’s Witnesses |
E159144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious organization unit |
C6552
|
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 unit Context triple: [Translation Services of Jehovah’s Witnesses, instanceOf, religious organization unit]
-
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 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.
-
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.
Jehovah’s Witnesses organizational unit
chosen
A Jehovah’s Witnesses organizational unit is a structured body within the denomination—such as a congregation, circuit, district, branch, or governing entity—responsible for coordinating worship, evangelizing activity, and administrative oversight for a defined group of members or geographic area.
-
E.
religious league
A religious league is an organized alliance of states, groups, or individuals united primarily by shared religious beliefs or interests to pursue common political, military, or social goals.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:24 p.m.