Triple
T19130961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Systematic theology at the University of Tübingen |
E468312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological subdiscipline |
C2089
|
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: theological subdiscipline Context triple: [Systematic theology at the University of Tübingen, instanceOf, theological subdiscipline]
-
A.
branch of Christian theology
chosen
A branch of Christian theology is a specialized field of study within Christian thought that systematically explores a particular aspect of faith, doctrine, or practice (such as Christology, ecclesiology, or soteriology).
-
B.
branch of Christian studies
A branch of Christian studies is a specialized field of theological inquiry that focuses on a particular aspect of Christian belief, practice, history, or scripture within the broader discipline of Christian theology.
-
C.
theological method
Theological method is the systematic approach and set of principles used to interpret religious sources, articulate doctrines, and relate faith to human experience and contemporary contexts.
-
D.
theological work
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
E.
theological concept
A theological concept is an abstract idea or principle used to understand, explain, or systematize beliefs about the nature of the divine, spiritual realities, and their relationship to the world and humanity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:05 p.m.