Triple
T27952214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snobbery and Decay |
E703456
|
entity |
| Predicate | usesHumourType |
P14479
|
FINISHED |
| Object | exaggeration |
—
|
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: exaggeration | Statement: [Snobbery and Decay, usesHumourType, exaggeration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHumourType Context triple: [Snobbery and Decay, usesHumourType, exaggeration]
-
A.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
B.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
-
C.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
humorousTone
Indicates that the related communication, expression, or interaction is characterized by humor, playfulness, or comedic intent.
-
E.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:25 p.m.