Triple
T7190423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disruption of 1843 |
E167676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Scottish religious history |
C1474
|
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: event in Scottish religious history Context triple: [Disruption of 1843, instanceOf, event in Scottish religious history]
-
A.
event in church history
chosen
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
B.
position in the Church of Scotland
A position in the Church of Scotland represents an official role or office within its Presbyterian governance and ministry structure, such as minister, elder, or deacon.
-
C.
event in Irish history
An event in Irish history is a significant occurrence or series of actions within Ireland’s past that influenced its political, social, cultural, or economic development.
-
D.
medieval Scottish bishopric
A medieval Scottish bishopric was an ecclesiastical jurisdiction headed by a bishop, overseeing the spiritual, administrative, and often political affairs of the Church within a defined region of Scotland during the Middle Ages.
-
E.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.