Triple
T36968553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Bay |
E914494
|
entity |
| Predicate | containsDarkHumor |
P45834
|
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: [Arizona Bay, containsDarkHumor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDarkHumor Context triple: [Arizona Bay, containsDarkHumor, true]
-
A.
hasHumorFunction
Indicates that something serves a humorous role or purpose, such as eliciting amusement, laughter, or comedic effect.
-
B.
usesNonVerbalHumor
Indicates that one entity employs non-verbal forms of humor, such as gestures, expressions, or physical actions, directed toward or involving another entity.
-
C.
hasComedyElements
chosen
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
D.
sharesSenseOfHumorWith
Indicates that two entities find similar things humorous and tend to laugh at or appreciate the same kinds of jokes or comedic styles.
-
E.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: May 3, 2026, 4:14 p.m.