Triple
T27640042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Organization |
E696564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal organization of the Church of Scientology |
C27650
|
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: internal organization of the Church of Scientology Context triple: [Sea Organization, instanceOf, internal organization of the Church of Scientology]
-
A.
Scientology facility
A Scientology facility is a building or complex owned or operated by the Church of Scientology where religious services, training, auditing, administration, and outreach activities are conducted.
-
B.
esoteric organization
An esoteric organization is a selectively accessible group structured around hidden knowledge, rituals, or practices that are revealed progressively to initiated members.
-
C.
organ of an international religious organization
chosen
An organ of an international religious organization is a formally established body or office within the organization that carries out specific governance, administrative, doctrinal, or representative functions on its behalf at the global level.
-
D.
internal law of a religious institute
The internal law of a religious institute is the body of norms, rules, and customs established by the institute itself to govern its members’ life, organization, discipline, and mission in harmony with the broader law of the Church.
-
E.
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.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:26 p.m.