Triple
T24209133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior General |
E600480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | leadership position in a religious institute |
C6234
|
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: leadership position in a religious institute Context triple: [Superior General, instanceOf, leadership position in a religious institute]
-
A.
religious leadership office
A religious leadership office is an organizational unit or position within a faith community responsible for guiding spiritual practice, administering religious functions, and overseeing the governance and pastoral care of its members.
-
B.
collective religious leadership
A collective religious leadership is a group of individuals who jointly hold and exercise spiritual, doctrinal, and organizational authority within a faith community.
-
C.
office in a religious order
chosen
An office in a religious order is a formally designated role or position within the community that carries specific spiritual, administrative, or pastoral responsibilities in service of the order’s mission and governance.
-
D.
Christian religious office
A Christian religious office is an institutional role or position within a Christian church or denomination, endowed with specific spiritual, liturgical, and administrative responsibilities and authority.
-
E.
religious institute member
A religious institute member is an individual who has formally joined a religious community or order, committing to its spiritual life, rules, and mission, often through vows or promises.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 11:53 p.m.