Triple
T35766377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canons of Ancyra |
E1034026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian church regulation |
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: early Christian church regulation Context triple: [canons of Ancyra, instanceOf, early Christian church regulation]
-
A.
early Christian church
The early Christian church was the loosely organized community of Jesus’ followers in the first few centuries CE, developing its beliefs, practices, and leadership structures as it spread throughout the Roman Empire and beyond.
-
B.
early Christian work
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
C.
early Christian building
An early Christian building is an architectural structure, often adapted from Roman civic forms like the basilica, designed for Christian worship, community gathering, and liturgical practices in the first centuries of Christianity.
-
D.
Christian ecclesial tradition
The Christian ecclesial tradition is the historically continuous, community-shaped pattern of faith, worship, doctrine, and governance that structures how Christians live, interpret, and hand on their understanding of the gospel across time.
-
E.
church order
chosen
Church order is the structured system of governance, rules, and practices that organizes the leadership, worship, discipline, and communal life of a Christian church or denomination.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.