Triple
T9304482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wittenberg Concord negotiations |
E223847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological negotiation |
C15570
|
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 negotiation Context triple: [Wittenberg Concord negotiations, instanceOf, theological negotiation]
-
A.
theological dialogue
chosen
A theological dialogue is a structured conversational exchange in which participants explore, question, and interpret religious beliefs, doctrines, and experiences in pursuit of deeper understanding or truth.
-
B.
theological dispute
A theological dispute is a conflict or debate between individuals or groups over differing interpretations of religious doctrines, beliefs, or sacred texts.
-
C.
theological proposition
A theological proposition is a declarative statement that asserts, explains, or interprets a claim about the nature, will, or actions of the divine within a religious or doctrinal framework.
-
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 consortium
A theological consortium is a collaborative association of religious scholars, institutions, and organizations dedicated to advancing the study, dialogue, and application of theological thought across traditions.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.