Triple
T22187123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archconfraternity of the Papal Grooms |
E548323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lay religious brotherhood |
C37390
|
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: lay religious brotherhood Context triple: [Archconfraternity of the Papal Grooms, instanceOf, lay religious brotherhood]
-
A.
Catholic lay brother
A Catholic lay brother is a male member of a religious institute who professes vows and lives the community’s spiritual life while typically focusing on manual, administrative, or apostolic work rather than ordained priestly ministry.
-
B.
religious-military order
A religious-military order is an organized group that combines a shared religious or spiritual mission with a structured, often hierarchical, military function or code of conduct.
-
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.
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.
-
E.
Catholic lay order
chosen
A Catholic lay order is an organized association of non-ordained faithful who commit to living out specific spiritual charisms and disciplines of the Catholic Church while remaining in their secular state of life.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.