Triple
T28211127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Leith |
E711172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Scottish Reformation |
C26999
|
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 the Scottish Reformation Context triple: [Siege of Leith, instanceOf, event in the Scottish Reformation]
-
A.
Scottish Reformer
A Scottish Reformer is a historical or contemporary figure from Scotland who actively advocates for significant religious, political, or social change, often challenging established institutions to promote reform.
-
B.
Protestant reform measure
A Protestant reform measure is a specific policy, decree, or action implemented to align religious, political, or social practices with Protestant theological principles and church governance.
-
C.
16th-century religious event
chosen
A 16th-century religious event is a historically situated occurrence, such as a council, reform, conflict, or ritual, that reflects and influences the era’s intense transformations in faith, doctrine, and church authority.
-
D.
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.
-
E.
event of the French Wars of Religion
An event of the French Wars of Religion is a historically specific occurrence—such as a battle, edict, massacre, negotiation, or political maneuver—directly related to the religious and civil conflicts between Catholics and Protestants in France between 1562 and 1598.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:39 p.m.