Triple
T32609683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicle of Fordun |
E833620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of Scotland |
C37219
|
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: history of Scotland Context triple: [Chronicle of Fordun, instanceOf, history of Scotland]
-
A.
history of the United Kingdom
The history of the United Kingdom traces the political, social, economic, and cultural development of England, Scotland, Wales, and Northern Ireland from their early origins through unification, empire, conflict, and modern democracy.
-
B.
Scottish history topic
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.
historic county of Scotland
A historic county of Scotland is a traditional territorial division that once served as an administrative and cultural unit, often retaining significance for identity, geography, and historical reference despite no longer having formal governmental functions.
-
D.
Scottish chronicle
chosen
A Scottish chronicle is a historical narrative or record that details events, rulers, and significant occurrences in Scotland’s past, often compiled by contemporary or near-contemporary writers.
-
E.
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.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.