Triple

T9293216
Position Surface form Disambiguated ID Type / Status
Subject Viridiana E223571 entity
Predicate censorshipStatusInSpain P40618 FINISHED
Object banned after initial release — 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: banned after initial release | Statement: [Viridiana, censorshipStatusInSpain, banned after initial release]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: censorshipStatusInSpain
Context triple: [Viridiana, censorshipStatusInSpain, banned after initial release]
  • A. statusInSpain
    Indicates the legal, social, or official condition or standing that an entity has within the jurisdiction of Spain.
  • B. censorshipLevel
    Indicates the degree or strictness of control, suppression, or restriction applied to information, media, or expression.
  • C. censorshipStatusAtTime chosen
    Indicates the censorship status of something at a specific point in time, capturing whether and how it was censored then.
  • D. censorshipReason
    Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
  • E. censorshipAuthority
    Indicates that one entity has the official power or responsibility to censor, restrict, or approve the information, media, or expression of another entity.
  • 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_69ca8422ddf881908a3f8f876c9f53aa completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd0898b3288190a627a58bfd9c57fe completed April 1, 2026, 11:59 a.m.
PD Predicate disambiguation batch_69cc7a5aeb748190afb89c6bbd2a6d6f completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:35 p.m.