Triple
T5999876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treatise on the Power and Primacy of the Pope |
E133566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran confessional document |
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: Lutheran confessional document Context triple: [Treatise on the Power and Primacy of the Pope, instanceOf, Lutheran confessional document]
-
A.
Catholic Church document
A Catholic Church document is an official written text issued or approved by Church authority that communicates, clarifies, or governs matters of faith, morals, liturgy, or discipline.
-
B.
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.
-
C.
16th-century theological document
A 16th-century theological document is a written work from the 1500s that articulates, debates, or codifies religious doctrines, beliefs, or practices within the historical context of Reformation-era Christianity.
-
D.
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.
-
E.
Lutheran church
A Lutheran church is a Christian congregation or building that follows the teachings of Martin Luther and the Lutheran Confessions, emphasizing salvation by grace through faith, the authority of Scripture, and liturgical worship.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:05 p.m.