Triple
T32609545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicle of Melrose |
E833617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish historical record |
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: Scottish historical record Context triple: [Chronicle of Melrose, instanceOf, Scottish historical record]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Scottish tradition
Scottish tradition encompasses the customs, rituals, arts, and social practices rooted in Scotland’s history and cultural heritage, including music, dance, storytelling, festivals, and clan-based identities.
-
E.
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.
- 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.