Triple
T34965719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After Dark |
E1008389
|
entity |
| Predicate | frameStoryTheme |
P150352
|
FINISHED |
| Object | loss of eyesight |
—
|
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: loss of eyesight | Statement: [After Dark, frameStoryTheme, loss of eyesight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameStoryTheme Context triple: [After Dark, frameStoryTheme, loss of eyesight]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
fictionalTheme
Indicates that a work, element, or context is centered around or characterized by a fictional theme or motif.
-
C.
primaryStoryThemes
chosen
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
narrativeFrameWork
Indicates a relationship where one element provides the structural or conceptual framework within which another element’s narrative is organized, interpreted, or presented.
- F. None of above.
Provenance (3 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4 p.m.