Triple
T9006864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Order of Saint Dominic |
E215165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Dominican Order |
C8742
|
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: branch of the Dominican Order Context triple: [Third Order of Saint Dominic, instanceOf, branch of the Dominican Order]
-
A.
Dominican tertiary
A Dominican tertiary is a layperson or secular cleric who, while living in the world, formally affiliates with the Dominican Order and follows its spirituality and rule adapted for non-monastic life.
-
B.
Dominican tertiary
A Dominican tertiary is a layperson or secular clergy member who formally affiliates with the Dominican Order, living out its spirituality and mission while remaining in their ordinary state of life.
-
C.
member of the Dominican Third Order
chosen
A member of the Dominican Third Order is a layperson or diocesan clergy who, while living in the secular world, formally associates with the Dominican Order and follows its spirituality, rule, and mission adapted to their state in life.
-
D.
Catholic religious order
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.
-
E.
organizational unit of the Society of Jesus
An organizational unit of the Society of Jesus is a formally structured subdivision (such as a province, region, or community) within the Jesuit order that coordinates governance, mission, and activities in a defined geographic or functional area.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:05 p.m.