Triple
T29041046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room 101 |
E737996
|
entity |
| Predicate | isHumorousVersionOf |
P43127
|
FINISHED |
| Object | the idea of ultimate personal fear or hatred |
—
|
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: the idea of ultimate personal fear or hatred | Statement: [Room 101, isHumorousVersionOf, the idea of ultimate personal fear or hatred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHumorousVersionOf Context triple: [Room 101, isHumorousVersionOf, the idea of ultimate personal fear or hatred]
-
A.
hasHumorousTreatmentOf
chosen
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
B.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
-
C.
isHumorousWork
Indicates that a work is intended to be humorous or comedic in nature.
-
D.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
E.
humorousTone
Indicates that the related communication, expression, or interaction is characterized by humor, playfulness, or comedic intent.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66040274c8190a7c9f08182edc8b7 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:01 a.m.