Triple
T22128793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Hair Day |
E546855
|
entity |
| Predicate | hasParodyContent |
P10352
|
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: [Bad Hair Day, hasParodyContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParodyContent Context triple: [Bad Hair Day, hasParodyContent, yes]
-
A.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
B.
hasParodyDebate
Indicates a relationship where one entity engages in or features a debate that parodies, satirizes, or humorously imitates another entity or its ideas.
-
C.
parodies
chosen
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
D.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
E.
hasNotableSatire
Indicates that one entity is recognized for containing or exemplifying a significant satirical treatment of the other 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12983acfc81908013f66acb31f198 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.