Triple
T33511655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio Relations Committee |
E858264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | film industry self-censorship body |
C9624
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: film industry self-censorship body Context triple: [Studio Relations Committee, instanceOf, film industry self-censorship body]
-
A.
film censor
A film censor is an authority or official responsible for reviewing, classifying, and potentially altering or restricting films based on legal, moral, or cultural standards.
-
B.
film censorship code
A film censorship code is a set of formal rules or guidelines that regulate the content, themes, and depictions allowed in motion pictures to align them with legal, moral, or cultural standards.
-
C.
film censorship organization
A film censorship organization is an authority or body that reviews, classifies, and may restrict or alter films based on legal, moral, cultural, or political standards before public exhibition.
-
D.
Hollywood self-regulatory body
chosen
A Hollywood self-regulatory body is an industry-run organization that creates, enforces, and oversees standards and guidelines for film and media content to preempt or reduce direct government regulation.
-
E.
film industry trust
A film industry trust is an organization or consortium that centralizes control over film production, distribution, and exhibition—often through shared ownership of patents, resources, or agreements—to coordinate activities and influence market power within the movie business.
- F. None of above.
Provenance (1 batch)
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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.