Triple
T10717364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not Myself Tonight |
E252711
|
entity |
| Predicate | containsExplicitContent |
P47549
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Not Myself Tonight, containsExplicitContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsExplicitContent Context triple: [Not Myself Tonight, containsExplicitContent, true]
-
A.
containsAdultContent
chosen
Indicates that the referenced item includes material intended for adults, such as explicit sexual, violent, or otherwise age-restricted content.
-
B.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
C.
containsGraphicViolence
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
D.
isExplicit
Indicates that something is stated clearly and directly, leaving no room for ambiguity or implied interpretation.
-
E.
depictsSex
Indicates that one entity visually represents or portrays sexual activity or sexual content involving 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6ff3566e88190b5c0c6d1b159dd45 |
completed | April 9, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.