Triple
T16466628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church electoral college of the Romanian Orthodox Church |
E399949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious organization component |
C34267
|
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 component Context triple: [Church electoral college of the Romanian Orthodox Church, instanceOf, religious organization component]
-
A.
religious entity
A religious entity is an organization, institution, or structured group formed around shared beliefs, practices, and rituals related to the sacred or divine.
-
B.
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.
-
C.
religious organization committee
chosen
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.
-
D.
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.
-
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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:11 a.m.