Triple
T38108275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arveragus |
E951581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chaucer character |
C30547
|
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: Chaucer character Context triple: [Arveragus, instanceOf, Chaucer character]
-
A.
character in The Canterbury Tales
chosen
A character in The Canterbury Tales is an individual pilgrim, each with distinct social background, personality, and motivations, who narrates a tale that reflects and critiques the values and tensions of late medieval English society.
-
B.
Decameron character
A Decameron character is an individual, either one of the ten storytellers or a figure within their tales, whose actions, traits, and experiences illustrate the social, moral, and emotional themes of Boccaccio’s narrative framework.
-
C.
Arthurian characters
Arthurian characters are the legendary figures—such as King Arthur, Merlin, Guinevere, and the Knights of the Round Table—who populate the mythic narratives of Arthurian romance, embodying ideals of chivalry, magic, betrayal, and heroism.
-
D.
Middle English author
A Middle English author is a writer who composed literary, religious, or historical works in the Middle English language, primarily between the late 11th and late 15th centuries in England.
-
E.
character in a chivalric romance
A character in a chivalric romance is an often idealized figure—such as a knight, noble lady, or sorcerer—whose adventures, virtues, and trials embody the codes of honor, courtly love, and heroic quest central to the narrative.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.