Triple
T33202214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U |
E849930
|
entity |
| Predicate | contentGuideline |
P161779
|
FINISHED |
| Object | no explicit sexual scenes |
—
|
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: no explicit sexual scenes | Statement: [U, contentGuideline, no explicit sexual scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentGuideline Context triple: [U, contentGuideline, no explicit sexual scenes]
-
A.
contentRestriction
Indicates that access to or use of certain content is limited or controlled based on specified rules or conditions.
-
B.
usesGuidelines
Indicates that one entity follows or applies a specified set of guidelines in performing an action or making decisions.
-
C.
topicOfGuidelines
chosen
Indicates that something serves as the subject or focus addressed by a set of guidelines.
-
D.
hasGuideline
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
-
E.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:30 a.m.