Triple
T32513095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight Misbehavin' |
E830986
|
entity |
| Predicate | openingSequenceGagType |
P90337
|
FINISHED |
| Object | couch gag |
—
|
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: couch gag | Statement: [Eight Misbehavin', openingSequenceGagType, couch gag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingSequenceGagType Context triple: [Eight Misbehavin', openingSequenceGagType, couch gag]
-
A.
openingSequenceType
Indicates the specific kind or category of an opening sequence associated with an entity or event.
-
B.
notableGag
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
C.
openingSequence
Indicates the initial ordered set of actions or events that begin a process, performance, or interaction.
-
D.
openingSequenceFormat
chosen
Indicates the specific structural or stylistic format used for an opening sequence in a work or presentation.
-
E.
openingCatchphrase
Indicates that one entity is a characteristic phrase or line regularly used by another entity at the beginning of a recurring performance, appearance, or communication.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1 a.m.