Triple
T3026700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Order of Dort |
E82792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical church governance text |
C11625
|
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: historical church governance text Context triple: [Church Order of Dort, instanceOf, historical church governance text]
-
A.
church document
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
-
B.
historic church body
A historic church body is a long-established Christian denomination or ecclesiastical organization whose identity, structure, and traditions have been shaped over centuries of continuous institutional and theological development.
-
C.
ecclesiastical document
chosen
An ecclesiastical document is an official written instrument issued or authorized by a church authority that records, communicates, or regulates matters of faith, doctrine, worship, or church governance.
-
D.
ecclesiastical authority
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
-
E.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.