Triple
T24439211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whisky Song |
E616212
|
entity |
| Predicate | usesSatireFor |
P114828
|
FINISHED |
| Object | social commentary |
—
|
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: social commentary | Statement: [Whisky Song, usesSatireFor, social commentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSatireFor Context triple: [Whisky Song, usesSatireFor, social commentary]
-
A.
hasSatiricalTone
Indicates that something expresses its content in a mocking, ironic, or humorous way to criticize or ridicule its subject.
-
B.
hasNotableSatire
Indicates that one entity is recognized for containing or exemplifying a significant satirical treatment of the other entity.
-
C.
literaryMovementSatirized
Indicates that a literary movement is the target of satire or critical ridicule in a given work or by a given author.
-
D.
usedForHumor
chosen
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
E.
roleInSatire
Indicates that an entity serves as a character, target, or contributing element within a satirical work or satirical 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297891f108190a98e55c900494d30 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.