Triple

T30056191
Position Surface form Disambiguated ID Type / Status
Subject Work Bitch E763738 entity
Predicate explicitTitleCensoredAs P70528 FINISHED
Object Work Work 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: Work Work | Statement: [Work Bitch, explicitTitleCensoredAs, Work Work]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: explicitTitleCensoredAs
Context triple: [Work Bitch, explicitTitleCensoredAs, Work Work]
  • A. hasCensorshipTitle
    Indicates that an entity has been assigned a specific title or designation for censorship or regulatory control purposes.
  • B. hasCensoredTitleVariant
    Indicates that an entity has an alternative version of its title that has been modified or censored, typically to remove or obscure sensitive or inappropriate content.
  • C. hasCensoredTitleVersion chosen
    Indicates that an entity has an alternative version of its title in which certain content has been censored, removed, or altered.
  • D. wasCensored
    Indicates that an entity’s content, expression, or communication was suppressed, altered, or restricted by an authority or controlling party.
  • E. containsExplicitWordInTitle
    Indicates that the title of an item includes at least one word that is considered explicit or profane.
  • 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_69f224716378819087a722e487832b70 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67a1a06588190b50edbd454df771b completed May 2, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69f673c664f08190b4d66cdc305e10db completed May 2, 2026, 9:59 p.m.
Created at: April 29, 2026, 6:56 p.m.