Triple
T10352670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland (as doctrinal standard in part) |
E243917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical doctrinal reception |
C8205
|
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: historical doctrinal reception Context triple: [Scotland (as doctrinal standard in part), instanceOf, historical doctrinal reception]
-
A.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
B.
New Testament tradition
New Testament tradition is the body of interpretive practices, teachings, and communal memories through which Christian communities have transmitted, received, and reshaped the writings and theology of the New Testament across history.
-
C.
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.
-
D.
doctrinal system
chosen
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.
historiographical tradition
A historiographical tradition is a coherent, historically developed approach to interpreting and writing about the past, characterized by shared methods, assumptions, and narrative patterns among historians.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:57 a.m.