Triple
T32512287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flaming Moe’s |
E830967
|
entity |
| Predicate | containsParody |
P177043
|
FINISHED |
| Object | Cheers-style opening sequence |
—
|
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: Cheers-style opening sequence | Statement: [Flaming Moe’s, containsParody, Cheers-style opening sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsParody Context triple: [Flaming Moe’s, containsParody, Cheers-style opening sequence]
-
A.
hasParodyStatus
Indicates that one entity is a parody, spoof, or humorous imitation of another entity or of a particular style or work.
-
B.
hasParodyOrAnswerSong
Indicates that one work is a parody of, or a direct answer/response to, another work.
-
C.
parodies
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
D.
conflictsWithParodies
Indicates that one entity is in conflict with another entity specifically in the context of parody, such as opposing, contradicting, or undermining the other through parody.
-
E.
parodiesWorkType
chosen
Indicates that one work humorously imitates or satirizes another work of a particular type or genre.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 1, 2026, 1 a.m.