Triple
T31532156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I'm Henry VIII, I Am" |
E804506
|
entity |
| Predicate | hasHumorousWordplay |
P75408
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: ["I'm Henry VIII, I Am", hasHumorousWordplay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumorousWordplay Context triple: ["I'm Henry VIII, I Am", hasHumorousWordplay, yes]
-
A.
hasIronicMeaning
Indicates that something conveys a meaning opposite to or incongruent with its literal expression, creating an ironic effect.
-
B.
usesDoubleEntendre
chosen
Indicates that one entity employs language or expressions with a double meaning, often to convey a hidden or suggestive message alongside a literal one.
-
C.
isWitty
Indicates that an entity consistently displays quick, clever, and humorous expression or behavior.
-
D.
humorReliesOn
Indicates that one entity’s humor depends on, is based on, or draws its effect from another entity.
-
E.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:01 p.m.