Triple
T23560696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muppet Labs |
E579227
|
entity |
| Predicate | notableRunningGag |
P52455
|
FINISHED |
| Object | Beaker being injured or endangered |
—
|
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: Beaker being injured or endangered | Statement: [Muppet Labs, notableRunningGag, Beaker being injured or endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRunningGag Context triple: [Muppet Labs, notableRunningGag, Beaker being injured or endangered]
-
A.
notableGag
chosen
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
B.
reasonForRunningGag
Indicates the underlying cause or explanation for why a particular running gag recurs.
-
C.
notableRoutine
Indicates a routine, practice, or sequence of actions that is especially prominent, well-known, or significant in some context.
-
D.
notableGaffe
Indicates that an entity is known for having made a significant mistake, blunder, or embarrassing error.
-
E.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af680ee88190a23a6f9fed7ae757 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:15 p.m.