Triple
T3239774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delirious |
E67938
|
entity |
| Predicate | containsHomophobicJokes |
P14479
|
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: [Delirious, containsHomophobicJokes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHomophobicJokes Context triple: [Delirious, containsHomophobicJokes, true]
-
A.
hasLGBTTheme
Indicates that the subject includes, features, or centrally involves lesbian, gay, bisexual, or transgender themes or issues.
-
B.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
C.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
D.
containsProfanity
Indicates that the referenced content includes one or more profane, vulgar, or offensive expressions.
-
E.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef4c0bc819095e4f84296fe7cb6 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.