Triple
T4944270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in the United States |
E111008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | part of Catholic Church |
C8666
|
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: part of Catholic Church Context triple: [Catholic Church in the United States, instanceOf, part of Catholic Church]
-
A.
rite of the Catholic Church
A rite of the Catholic Church is a distinct liturgical, theological, spiritual, and disciplinary tradition by which the Church’s universal faith is expressed and celebrated in worship and practice.
-
B.
Eastern Catholic particular church
chosen
An Eastern Catholic particular church is an autonomous, self-governing community of faithful within the Catholic Church that follows an Eastern Christian liturgical, theological, and spiritual tradition while remaining in full communion with the Pope.
-
C.
Eastern Catholic particular church
An Eastern Catholic particular church is an autonomous, self-governing community of faithful within the Catholic Church that follows a distinct Eastern liturgical, theological, spiritual, and canonical tradition while remaining in full communion with the Pope.
-
D.
Catholic Church document
A Catholic Church document is an official written text issued or approved by Church authority that communicates, clarifies, or governs matters of faith, morals, liturgy, or discipline.
-
E.
Roman Catholic church
A Roman Catholic church is a Christian place of worship that serves as a local community’s center for liturgy, sacraments, and prayer within the Roman Catholic tradition.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.