Triple
T36975047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulula.com |
E914673
|
entity |
| Predicate | usesHumorIn |
P172889
|
FINISHED |
| Object | in-flight announcements |
—
|
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: in-flight announcements | Statement: [Kulula.com, usesHumorIn, in-flight announcements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHumorIn Context triple: [Kulula.com, usesHumorIn, in-flight announcements]
-
A.
usesHumorToExplore
Indicates using humor as a means or tool to examine, reflect on, or delve into a subject, situation, or relationship.
-
B.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
-
C.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
hasHumorFunction
chosen
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
-
E.
humorSetting
Indicates a relationship where one entity specifies or controls the level, style, or presence of humor applied to another entity or context.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.