Triple
T14350505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twelve Reasons to Die |
E355837
|
entity |
| Predicate | storyDevice |
P35676
|
FINISHED |
| Object | resurrection through vinyl records |
—
|
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: resurrection through vinyl records | Statement: [Twelve Reasons to Die, storyDevice, resurrection through vinyl records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyDevice Context triple: [Twelve Reasons to Die, storyDevice, resurrection through vinyl records]
-
A.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
B.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
D.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f4e1e588190bdc7aaf7a2819948 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.