Triple
T11860213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Summoner's Tale |
E282138
|
entity |
| Predicate | climacticJoke |
P52455
|
FINISHED |
| Object | division of a fart among friars |
—
|
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: division of a fart among friars | Statement: [The Summoner's Tale, climacticJoke, division of a fart among friars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climacticJoke Context triple: [The Summoner's Tale, climacticJoke, division of a fart among friars]
-
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.
typeOfClimax
Indicates the specific kind or category of climax that characterizes an event, narrative, or process.
-
D.
hasClimaxAt
Indicates that an event, narrative, or process reaches its most intense or decisive point at a specified time, place, or segment.
-
E.
notableGag
chosen
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.