Triple
T17455317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic hierarchy in Guatemala |
E425012
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious organization 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 organization structure Context triple: [Catholic hierarchy in Guatemala, instanceOf, religious organization 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.
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.
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.
-
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 commission
A religious organization commission is a formal body established to oversee, regulate, or advise on the activities, governance, and compliance of religious institutions within a defined jurisdiction or denomination.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.