Triple

T28057827
Position Surface form Disambiguated ID Type / Status
Subject Lapsis E709015 entity
Predicate hasSatiricalAspect P98013 FINISHED
Object gig economy labor practices 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: gig economy labor practices | Statement: [Lapsis, hasSatiricalAspect, gig economy labor practices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSatiricalAspect
Context triple: [Lapsis, hasSatiricalAspect, gig economy labor practices]
  • A. hasSatiricalTone
    Indicates that something expresses its content in a mocking, ironic, or humorous way to criticize or ridicule its subject.
  • B. hasNotableSatire chosen
    Indicates that one entity is recognized for containing or exemplifying a significant satirical treatment of the other entity.
  • C. satirizedBy
    Indicates that the subject is the target or object of satire created or performed by the specified entity.
  • D. isSatiricalCycleComponent
    Indicates that something functions as a constituent part of a larger satirical cycle or series.
  • E. hasHumorousTreatmentOf
    Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
  • 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_69ef9b6eb6d88190a3fea236eb0f7bed completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f6aaf50be08190a2b62a6d881f8aee completed May 3, 2026, 1:55 a.m.
PD Predicate disambiguation batch_69f6aa1c555081908787dbf76147f180 completed May 3, 2026, 1:51 a.m.
Created at: April 27, 2026, 8:37 p.m.