Triple
T13699131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | When the People Cheer |
E328468
|
entity |
| Predicate | hasSatiricalContent |
P98013
|
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: [When the People Cheer, hasSatiricalContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSatiricalContent Context triple: [When the People Cheer, hasSatiricalContent, yes]
-
A.
hasNotableSatire
chosen
Indicates that one entity is recognized for containing or exemplifying a significant satirical treatment of the other entity.
-
B.
isSatiricalCycleComponent
Indicates that something functions as a constituent part of a larger satirical cycle or series.
-
C.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
D.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
E.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.