Triple
T37719649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Superiors General |
E939548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association of religious superiors |
C64462
|
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: association of religious superiors Context triple: [Union of Superiors General, instanceOf, association of religious superiors]
-
A.
priestly sodality
A priestly sodality is a structured association of clergy united by shared spiritual practices, mutual support, and a common commitment to specific religious ideals or ministries.
-
B.
religious order administration
Religious order administration is the organized system of governance, management, and support that oversees the spiritual, communal, and temporal affairs of a religious community or institution.
-
C.
religious order presence
The "religious order presence" class represents the existence, extent, and characteristics of one or more organized religious communities or orders within a given context, such as a location, institution, or time period.
-
D.
clerical society of apostolic life of pontifical right
A clerical society of apostolic life of pontifical right is a community of priests, recognized and directly governed by the Holy See, who live fraternally and pursue specific apostolic works without taking religious vows.
-
E.
office in a religious order
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.
- F. None of above. chosen
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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.