Triple
T38466413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | monastic community of Lérins Abbey |
E912578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic monastic community |
C1776
|
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: Catholic monastic community Context triple: [monastic community of Lérins Abbey, instanceOf, Catholic monastic community]
-
A.
Catholic religious house
A Catholic religious house is a residence where members of a Catholic religious community live, pray, and carry out their spiritual and communal activities under a shared rule of life.
-
B.
Christian monastic federation
A Christian monastic federation is an organized association of autonomous monasteries or religious communities that share a common spiritual tradition, governance framework, and mutual support while retaining their individual identities.
-
C.
Benedictine congregation
A Benedictine congregation is an autonomous association of monasteries or religious communities that follow the Rule of St. Benedict and share common governance, spiritual traditions, and mission within the wider Benedictine Confederation.
-
D.
Catholic lay order
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.
-
E.
Catholic religious order
chosen
A Catholic religious order is a community of men or women in the Catholic Church who profess public vows and live a shared spiritual, communal, and often apostolic life according to a specific rule and charism.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.