Triple
T13645254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldorf |
E326084
|
entity |
| Predicate | targetOfJokes |
P63937
|
FINISHED |
| Object | performers on stage |
—
|
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: performers on stage | Statement: [Waldorf, targetOfJokes, performers on stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfJokes Context triple: [Waldorf, targetOfJokes, performers on stage]
-
A.
humorSource
chosen
Indicates that one entity is the origin or cause of humor experienced in relation to another entity.
-
B.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or context.
-
C.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
-
D.
hasHumorType
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
E.
notablePrankTarget
Indicates that the subject is a well-known or frequent target of pranks carried out by the object.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.