Triple
T25500791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dick Emery Show |
E639103
|
entity |
| Predicate | hasCatchphrases |
P53722
|
FINISHED |
| Object | recurring comedic catchphrases |
—
|
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: recurring comedic catchphrases | Statement: [The Dick Emery Show, hasCatchphrases, recurring comedic catchphrases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchphrases Context triple: [The Dick Emery Show, hasCatchphrases, recurring comedic catchphrases]
-
A.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
-
B.
hasCatchphraseStatus
Indicates whether an entity’s phrase or expression holds the status of being recognized as a catchphrase.
-
C.
notableCatchphraseUser
Indicates that the subject is a person who is notably associated with using a particular catchphrase.
-
D.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
-
E.
featuresCatchphrase
chosen
Indicates that an entity prominently includes or is associated with a particular catchphrase.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 2:42 p.m.