Triple
T6967397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Sickness and in Health |
E161522
|
entity |
| Predicate | featuresHumourStyle |
P14479
|
FINISHED |
| Object | black 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: black comedy | Statement: [In Sickness and in Health, featuresHumourStyle, black comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHumourStyle Context triple: [In Sickness and in Health, featuresHumourStyle, black comedy]
-
A.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
B.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or context.
-
C.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
-
D.
humorSource
Indicates that one entity is the origin or cause of humor experienced in relation to another entity.
-
E.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1373d88190967b42630f8688d6 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.