Triple
T35512341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywoo |
E1026316
|
entity |
| Predicate | targetAudienceOfSatire |
P198425
|
FINISHED |
| Object | Hollywood system |
—
|
NE NERFINISHED |
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: Hollywood system | Statement: [Hollywoo, targetAudienceOfSatire, Hollywood system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceOfSatire Context triple: [Hollywoo, targetAudienceOfSatire, Hollywood system]
-
A.
politicalOrientationOfSatire
Indicates the political stance or ideology that a piece of satire is targeting, expressing, or associated with.
-
B.
humourTarget
Indicates that one entity is the object or focus of another entity’s humor, such as jokes, teasing, or comedic commentary.
-
C.
satirizedBy
Indicates that the subject is the target or object of satire created or performed by the specified entity.
-
D.
hasSatiricalTone
Indicates that something expresses its content in a mocking, ironic, or humorous way to criticize or ridicule its subject.
-
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. chosen
Provenance (4 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
| PDg | Predicate description generation | batch_69fee25c7c548190a2c6e50074a33da4 |
completed | May 9, 2026, 7:29 a.m. |
Created at: May 3, 2026, 4:04 p.m.