Triple
T4760129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran Church (for reading and instruction) |
E105679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran doctrinal tradition |
C12187
|
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 doctrinal tradition Context triple: [Lutheran Church (for reading and instruction), instanceOf, Lutheran doctrinal tradition]
-
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.
movement within Lutheranism
chosen
A movement within Lutheranism is a distinct trend or group that emphasizes particular theological, liturgical, social, or cultural emphases while remaining rooted in core Lutheran confessions and identity.
-
C.
Lutheran diocese
A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
-
D.
Western liturgical tradition
The Western liturgical tradition is the historical and theological stream of Christian worship practices, rites, and calendars that developed primarily in Western Europe, especially within the Roman Catholic, Anglican, and Protestant churches.
-
E.
Christian doctrine
Christian doctrine is the organized body of beliefs and teachings derived from the Bible and Christian tradition that defines the faith’s understanding of God, salvation, morality, and the church.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.