Triple
T2600590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Canterbury Tales |
E58332
|
entity |
| Predicate | frameStoryCharacters |
P39526
|
FINISHED |
| Object | group of pilgrims |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: group of pilgrims | Statement: [The Canterbury Tales, frameStoryCharacters, group of pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameStoryCharacters Context triple: [The Canterbury Tales, frameStoryCharacters, group of pilgrims]
-
A.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
B.
narrativeSourceCharacter
Indicates that a particular character serves as the source or narrator from whose perspective the narrative is presented.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
- F. None of above. chosen
Provenance (4 batches)
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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:49 p.m.