Triple
T29285418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golf Specialist |
E742495
|
entity |
| Predicate | hasMannerOfHumor |
P14479
|
FINISHED |
| Object | slapstick |
—
|
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: slapstick | Statement: [The Golf Specialist, hasMannerOfHumor, slapstick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMannerOfHumor Context triple: [The Golf Specialist, hasMannerOfHumor, slapstick]
-
A.
hasHumorFunction
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
-
B.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
C.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
-
D.
usesHumorToExplore
Indicates using humor as a means or tool to examine, reflect on, or delve into a subject, situation, or relationship.
-
E.
usesNonVerbalHumor
Indicates that one entity employs non-verbal forms of humor, such as gestures, expressions, or physical actions, directed toward or involving 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 28, 2026, 12:57 p.m.