Triple
T21993112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun the Sheep Movie |
E543136
|
entity |
| Predicate | featuresNonverbalHumor |
P114828
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shaun the Sheep Movie, featuresNonverbalHumor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNonverbalHumor Context triple: [Shaun the Sheep Movie, featuresNonverbalHumor, true]
-
A.
nonVerbalIn
Indicates that an entity is present in a location or context without using spoken or written language, relying instead on non-verbal communication or behavior.
-
B.
nonVerbalPossible
Indicates that the relationship or action can occur or be expressed without the use of spoken or written language.
-
C.
usedForHumor
chosen
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
-
E.
humorousTone
Indicates that the related communication, expression, or interaction is characterized by humor, playfulness, or comedic intent.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1270f77fc8190aadcc02760d65ac0 |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:15 p.m.