Triple

T18140072
Position Surface form Disambiguated ID Type / Status
Subject Charlotte for Ever E434236 entity
Predicate hasControversialThemes P81772 FINISHED
Object sexual themes 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: sexual themes | Statement: [Charlotte for Ever, hasControversialThemes, sexual themes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasControversialThemes
Context triple: [Charlotte for Ever, hasControversialThemes, sexual themes]
  • A. hasControversialAspect chosen
    Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
  • B. controversialBecause
    Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
  • C. hasControversialLyrics
    Indicates that the lyrics associated with an entity are considered contentious, offensive, or likely to provoke public disagreement or debate.
  • D. controversialWork
    Indicates that a work is the subject of significant public disagreement, debate, or dispute regarding its content, impact, or acceptability.
  • E. controversialStatus
    Indicates that the subject is associated with debate, dispute, or disagreement regarding its acceptance, validity, or appropriateness.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de0a59d08190be74c1ecc00a8f3a completed April 19, 2026, 1:52 p.m.
PD Predicate disambiguation batch_69e43317d11c81908d1dc14921566b47 completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:29 a.m.