Triple
T29345656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I don't get no respect" |
E744163
|
entity |
| Predicate | memeticUse |
P114828
|
FINISHED |
| Object | expression of comic frustration |
—
|
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: expression of comic frustration | Statement: ["I don't get no respect", memeticUse, expression of comic frustration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memeticUse Context triple: ["I don't get no respect", memeticUse, expression of comic frustration]
-
A.
associatedMeme
Indicates that one entity is linked or connected to another entity in the context of a meme (e.g., as its related or corresponding meme).
-
B.
featuresMeme
Indicates that something includes, presents, or prominently displays a particular meme.
-
C.
usedForHumor
chosen
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
E.
usedHyperbolically
Indicates that the action or property is being expressed with deliberate exaggeration for emphasis or effect, rather than as a literal statement.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66957a1f0819094c1be1055b97f47 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:01 p.m.