Triple
T35660451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaches Ain't Ready |
E1030417
|
entity |
| Predicate | makesPunOn |
P18159
|
FINISHED |
| Object | "bitches ain't ready" phrase structure |
—
|
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: "bitches ain't ready" phrase structure | Statement: [Beaches Ain't Ready, makesPunOn, "bitches ain't ready" phrase structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesPunOn Context triple: [Beaches Ain't Ready, makesPunOn, "bitches ain't ready" phrase structure]
-
A.
namePunOn
chosen
Indicates that one entity’s name is a play on, parody of, or humorous variation of another entity’s name.
-
B.
isWitty
Indicates that an entity consistently displays quick, clever, and humorous expression or behavior.
-
C.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
hasHumorFunction
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
-
E.
punchlineStructure
Indicates the structural role or pattern a punchline follows within a joke or humorous setup.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7aa7b88190a52ff8ef9ceddf54 |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.