Triple
T27103112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto Gets the Paper |
E686492
|
entity |
| Predicate | featuresTypeOfHumor |
P14479
|
FINISHED |
| Object | physical comedy |
—
|
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: physical comedy | Statement: [Pluto Gets the Paper, featuresTypeOfHumor, physical comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTypeOfHumor Context triple: [Pluto Gets the Paper, featuresTypeOfHumor, physical comedy]
-
A.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
B.
genreOfComedy
Indicates that something belongs to or is categorized within the comedy genre.
-
C.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or context.
-
D.
hasHumorFunction
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
-
E.
humorReliesOn
Indicates that one entity’s humor depends on, is based on, or draws its effect from another entity.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 8:49 a.m.