Triple
T5451165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig Disputation (1519) |
E122372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological disputation |
C3649
|
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 disputation Context triple: [Leipzig Disputation (1519), instanceOf, theological disputation]
-
A.
theological dispute
chosen
A theological dispute is a conflict or debate between individuals or groups over differing interpretations of religious doctrines, beliefs, or sacred texts.
-
B.
theological dialogue
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.
-
C.
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.
-
D.
religious controversy
Religious controversy is a sustained conflict or debate arising from differing beliefs, doctrines, practices, or interpretations within or between religious traditions.
-
E.
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.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.