Triple
T33123243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominican Province of the Holy Rosary |
E847656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | missionary province |
C26089
|
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: missionary province Context triple: [Dominican Province of the Holy Rosary, instanceOf, missionary province]
-
A.
missionary diocese
A missionary diocese is a territorial ecclesiastical jurisdiction, often in a developing or non-traditional Christian region, established to organize and advance the church’s missionary, pastoral, and evangelizing work under the authority of a bishop or equivalent leader.
-
B.
Dominican province
A Dominican province is an administrative territorial unit of the Order of Preachers that groups together Dominican friaries and ministries within a specific geographic region under a common governance.
-
C.
missionary society
A missionary society is an organized religious group dedicated to planning, supporting, and carrying out missionary work, often including evangelism, education, and social services in domestic or foreign fields.
-
D.
religious province-level entity
chosen
A religious province-level entity is an administrative division within a religious organization that oversees and coordinates the activities, governance, and spiritual leadership of multiple subordinate units (such as dioceses, districts, or congregations) within a defined geographic area.
-
E.
mission church
A mission church is a religious building or congregation established by a parent church or missionary organization to serve a specific community, often in a developing or newly evangelized 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.