Triple
T18895474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höhere Wesen befahlen: rechte obere Ecke schwarz malen! |
E462196
|
entity |
| Predicate | hasHumorousIntent |
P116540
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Höhere Wesen befahlen: rechte obere Ecke schwarz malen!, hasHumorousIntent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumorousIntent Context triple: [Höhere Wesen befahlen: rechte obere Ecke schwarz malen!, hasHumorousIntent, true]
-
A.
hasHumorType
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
B.
hasIronicMeaning
Indicates that something conveys a meaning opposite to or incongruent with its literal expression, creating an ironic effect.
-
C.
humorousTone
chosen
Indicates that the related communication, expression, or interaction is characterized by humor, playfulness, or comedic intent.
-
D.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
E.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47eb0688190882c68d0d6fa9348 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.