Triple
T13776875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Order of the Christian Reformed Church in North America |
E331031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church order |
C34155
|
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: church order Context triple: [Church Order of the Christian Reformed Church in North America, instanceOf, church order]
-
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.
church organization
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
-
C.
religious order administration
Religious order administration is the organized system of governance, management, and support that oversees the spiritual, communal, and temporal affairs of a religious community or institution.
-
D.
Kirchliches Gremium
Ein kirchliches Gremium ist eine organisierte Gruppe von Personen innerhalb einer Kirche, die gemeinsam Entscheidungen trifft, Beratungsaufgaben wahrnimmt oder bestimmte Verantwortungsbereiche in der kirchlichen Leitung und Verwaltung ausübt.
-
E.
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.
- F. None of above. chosen
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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:10 p.m.