Triple
T30125235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish devolution referendum, 1979 |
E765677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish political event |
C48358
|
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: Scottish political event Context triple: [Scottish devolution referendum, 1979, instanceOf, Scottish political event]
-
A.
Scottish historical movement
A Scottish historical movement is a collective effort or trend within Scotland’s past, driven by social, political, cultural, or economic forces, that significantly shaped the nation’s identity and development over time.
-
B.
Scottish history topic
chosen
A Scottish history topic is a specific subject or theme related to Scotland’s past, encompassing its political events, social developments, cultural changes, or notable figures across different historical periods.
-
C.
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.
-
D.
Scottish civil conflict
Scottish civil conflict refers to internal political, religious, and military struggles within Scotland, often involving rival noble factions, competing claims to the throne, and clashes over governance and national identity.
-
E.
Scottish legal case
A Scottish legal case is a formal dispute brought before a Scottish court or tribunal to interpret and apply Scots law to specific facts and determine the rights and obligations of the parties involved.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:14 p.m.