Triple
T36047655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Church hierarchy |
E1042717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious organizational structure |
C16072
|
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 organizational structure Context triple: [Christian Church hierarchy, instanceOf, religious organizational structure]
-
A.
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.
-
B.
church organization
chosen
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
-
C.
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.
-
D.
religious organization committee
A religious organization committee is a structured group within a faith-based institution responsible for planning, coordinating, and overseeing specific religious, administrative, or community activities in alignment with the organization’s beliefs and goals.
-
E.
religious organization subgroup
A religious organization subgroup is a distinct division within a larger religious body, formed around specific doctrines, practices, demographics, or administrative functions while remaining affiliated with the parent organization.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.