Triple
T23023816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Württemberg Confession |
E573243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran confession of faith |
C40523
|
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 confession of faith Context triple: [Württemberg Confession, instanceOf, Lutheran confession of faith]
-
A.
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.
-
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.
Lutheran systematic theology
Lutheran systematic theology is the ordered, doctrinal articulation of Christian faith from a Lutheran perspective, integrating Scripture, the Lutheran Confessions, and theological tradition into a coherent framework for belief and practice.
-
D.
religious confession of faith
chosen
A religious confession of faith is a formal, structured statement that summarizes and publicly declares the core beliefs and doctrines held by a religious community or tradition.
-
E.
work of Lutheran orthodoxy
A work of Lutheran orthodoxy is a theological or doctrinal text produced within the Lutheran tradition, especially between the late 16th and early 18th centuries, that systematically articulates and defends confessional Lutheran beliefs against contemporary challenges.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:52 p.m.