Triple
T7019586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | congregation Watchtower Study |
E162785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jehovah’s Witnesses meeting |
C18862
|
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: Jehovah’s Witnesses meeting Context triple: [congregation Watchtower Study, instanceOf, Jehovah’s Witnesses meeting]
-
A.
Jehovah's Witnesses facility
A Jehovah's Witnesses facility is a building or complex used by members of the Jehovah's Witnesses religious organization for worship, meetings, training, administration, or literature production and distribution.
-
B.
Jehovah’s Witnesses organizational unit
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.
-
C.
religious assembly
chosen
A religious assembly is a gathering of individuals who come together to participate in shared spiritual, worship, or faith-based activities according to a common religious tradition or belief system.
-
D.
Jehovah's Witness
A Jehovah's Witness is a member of a Christian-based religious movement known for door-to-door evangelism, nontrinitarian beliefs, and adherence to teachings of the Watch Tower Bible and Tract Society.
-
E.
Jehovah's Witnesses family
A Jehovah's Witnesses family is a household whose members practice the Jehovah's Witness faith together, sharing distinctive beliefs, worship routines, and lifestyle choices shaped by their religious doctrines.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:34 p.m.