Triple
T2184083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Will and Testament of the Springfield Presbytery |
E49110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian theological text |
C5069
|
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: Christian theological text Context triple: [The Last Will and Testament of the Springfield Presbytery, instanceOf, Christian theological text]
-
A.
Christian sacred text
A Christian sacred text is a written work regarded by Christians as divinely inspired or authoritative for faith, doctrine, and practice, such as the Bible and related canonical or devotional writings.
-
B.
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.
-
C.
theological document
chosen
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
-
D.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
-
E.
religious scripture
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.