Triple
T28208136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales from the Crypt (1972 film) |
E717085
|
entity |
| Predicate | hasFramingNarrative |
P7324
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tales from the Crypt (1972 film), hasFramingNarrative, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFramingNarrative Context triple: [Tales from the Crypt (1972 film), hasFramingNarrative, yes]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
hasNoFrameNarrative
Indicates that a narrative work lacks an overarching frame story or framing device that encloses or contextualizes its main narrative.
-
C.
narrativeFrame
chosen
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
D.
hasFramingStoryTitle
Indicates that an entity is associated with the title of a framing story that encloses or contextualizes its main narrative content.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 10:36 p.m.