Triple
T11339973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panic in the Mailroom |
E268568
|
entity |
| Predicate | containsTypeOfHumor |
P14479
|
FINISHED |
| Object | physical comedy |
—
|
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: physical comedy | Statement: [Panic in the Mailroom, containsTypeOfHumor, physical comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTypeOfHumor Context triple: [Panic in the Mailroom, containsTypeOfHumor, physical comedy]
-
A.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
B.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
C.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or context.
-
D.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
E.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea01c6c08190910a6ce8fb7e186d |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.