Triple
T30825476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deadly Attachment |
E785049
|
entity |
| Predicate | containsRunningGag |
P58285
|
FINISHED |
| Object | misuse of authority by Captain Mainwaring |
—
|
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: misuse of authority by Captain Mainwaring | Statement: [The Deadly Attachment, containsRunningGag, misuse of authority by Captain Mainwaring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRunningGag Context triple: [The Deadly Attachment, containsRunningGag, misuse of authority by Captain Mainwaring]
-
A.
hasRecurringGag
Indicates that a particular joke, situation, or comedic element repeatedly appears in relation to an entity (such as a character, series, or work).
-
B.
reasonForRunningGag
Indicates the underlying cause or explanation for why a particular running gag recurs.
-
C.
featuresRunningGag
chosen
Indicates that the subject includes or makes use of a recurring joke or humorous motif.
-
D.
notableGag
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
E.
hasEvaluationGag
Indicates that an entity is subject to a restriction or prohibition on disclosing or sharing evaluations, assessments, or reviews related to it.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 29, 2026, 8:44 p.m.