Triple
T23262868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Chaucerianism |
E582058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish literature movement |
C47443
|
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 literature movement Context triple: [Scottish Chaucerianism, instanceOf, Scottish literature movement]
-
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 literary work
A Scottish literary work is a piece of writing—such as a novel, poem, play, or essay—created by a Scottish author or strongly rooted in Scotland’s culture, history, language, or landscape.
-
C.
Scottish cultural work
A Scottish cultural work is a creative or intellectual production—such as literature, music, film, art, or performance—that is produced in Scotland or by Scottish creators and meaningfully reflects, represents, or engages with Scottish history, society, or identity.
-
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.
Scottish literary manuscript
A Scottish literary manuscript is a handwritten or typescript document originating in or closely connected to Scotland that records the creation, revision, or transmission of literary works, such as poetry, fiction, drama, or essays.
- F. None of above. chosen
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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:11 p.m.