Triple
T10727326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Princeton theology |
E252983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reformed theological tradition |
C23473
|
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: Reformed theological tradition Context triple: [Old Princeton theology, instanceOf, Reformed theological tradition]
-
A.
Reformed theology text
A Reformed theology text is a written work that systematically presents and explains Christian doctrine from the perspective of the Reformed tradition, emphasizing God’s sovereignty, covenant theology, and the authority of Scripture.
-
B.
Reformed confessional status
Reformed confessional status is the recognized standing of a church, minister, or individual as formally subscribing to and being governed by a specific historic Reformed confession of faith.
-
C.
Dutch Reformed tradition
chosen
The Dutch Reformed tradition is a branch of Protestant Christianity rooted in the Reformation in the Netherlands, characterized by Reformed theology, covenantal worship, and a strong emphasis on confessional standards such as the Three Forms of Unity.
-
D.
Calvinist
A Calvinist is a follower of the Protestant theological tradition rooted in the teachings of John Calvin, emphasizing God’s sovereignty, predestination, and salvation by grace alone.
-
E.
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.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:14 p.m.