Triple

T14657892
Position Surface form Disambiguated ID Type / Status
Subject Tie Me Up! Tie Me Down! E344155 entity
Predicate ratingControversy P42781 FINISHED
Object MPAA NC-17 rating dispute 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: MPAA NC-17 rating dispute | Statement: [Tie Me Up! Tie Me Down!, ratingControversy, MPAA NC-17 rating dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ratingControversy
Context triple: [Tie Me Up! Tie Me Down!, ratingControversy, MPAA NC-17 rating dispute]
  • A. controversialBecause
    Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
  • B. controversy
    Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
  • C. controversyType chosen
    Indicates the specific kind or category of controversy associated with an entity or situation.
  • D. viewOnControversy
    Indicates a stance, opinion, or perspective that an entity holds regarding a controversial issue or topic.
  • E. hasControversialAspect
    Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
  • 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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb51b6a248190a44050c0e0ec2d16 completed April 14, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69de6576f0208190aa94d995e797ac38 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:27 a.m.