Triple
T2607138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encyclopaedie der Heilige Godgeleerdheid |
E58686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | systematic theology work |
C5743
|
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: systematic theology work Context triple: [Encyclopaedie der Heilige Godgeleerdheid, instanceOf, systematic theology work]
-
A.
theological work
chosen
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.
-
B.
theological journal
A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
-
C.
theological library
A theological library is a specialized collection of books, manuscripts, digital resources, and reference materials focused on religious studies, sacred texts, theology, and related disciplines, organized to support research, education, and spiritual inquiry.
-
D.
doctrinal system
A doctrinal system is an organized, coherent set of principles, beliefs, or teachings that provides a structured framework for understanding, interpreting, and guiding thought or behavior within a particular domain.
-
E.
theological document
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:49 p.m.