Triple
T26802311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columban church |
E671133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian church tradition |
C5159
|
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: Christian church tradition Context triple: [Columban church, instanceOf, Christian church tradition]
-
A.
Catholic Church tradition
Catholic Church tradition is the body of beliefs, practices, liturgy, teachings, and customs handed down through the centuries in the Catholic community, alongside Scripture, as a living transmission of the faith.
-
B.
Christian church
chosen
A Christian church is a community of believers in Jesus Christ who gather for worship, teaching, sacraments, fellowship, and service according to Christian faith and practice.
-
C.
Anglican tradition
The Anglican tradition is a Christian faith stream rooted in the Church of England that blends Catholic and Reformed elements, emphasizing liturgical worship, the authority of Scripture, and a via media (middle way) in theology and practice.
-
D.
Christian monastic tradition
The Christian monastic tradition is a way of life within Christianity in which individuals or communities withdraw from ordinary society to devote themselves to prayer, contemplation, disciplined spiritual practice, and communal or solitary living under religious vows.
-
E.
Western liturgical tradition
The Western liturgical tradition is the historical and theological stream of Christian worship practices, rites, and calendars that developed primarily in Western Europe, especially within the Roman Catholic, Anglican, and Protestant churches.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:24 a.m.