Triple
T29932262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Aristocrats |
E760246
|
entity |
| Predicate | centralJoke |
P172889
|
FINISHED |
| Object | The Aristocrats joke |
—
|
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: The Aristocrats joke | Statement: [The Aristocrats, centralJoke, The Aristocrats joke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralJoke Context triple: [The Aristocrats, centralJoke, The Aristocrats joke]
-
A.
humorSource
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.
humourTarget
Indicates that one entity is the object or focus of another entity’s humor, such as jokes, teasing, or comedic commentary.
-
D.
punchlineStructure
Indicates the structural role or pattern a punchline follows within a joke or humorous setup.
-
E.
hasHumorFunction
chosen
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 6:18 p.m.