Triple

T32089226
Position Surface form Disambiguated ID Type / Status
Subject Séverine Serizy E819539 entity
Predicate hasFantasyLife P192784 FINISHED
Object sadomasochistic scenarios 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: sadomasochistic scenarios | Statement: [Séverine Serizy, hasFantasyLife, sadomasochistic scenarios]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFantasyLife
Context triple: [Séverine Serizy, hasFantasyLife, sadomasochistic scenarios]
  • A. hasFantasyElement
    Indicates that something includes or involves elements characteristic of fantasy, such as magic, mythical creatures, or imaginary worlds.
  • B. hasFictionalPet
    Indicates that an entity has, owns, or is associated with a pet that is fictional or imaginary.
  • C. usedInFantasySportsPlatforms
    Indicates that something (such as data, content, or a feature) is utilized within fantasy sports platforms for gameplay, management, or related functionality.
  • D. hasFictionalGoal
    Indicates that an entity is associated with a goal or objective that exists only within a fictional, imagined, or narrative context.
  • E. hasFictionalProperty
    Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
  • F. None of above. chosen

Provenance (4 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_69f349004b2481908ce2e50af0d579a8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fd2a215d6c8190a1a428ccaee603f1 completed May 8, 2026, 12:11 a.m.
PD Predicate disambiguation batch_69fd28ef19688190bb8370f2812a43e7 completed May 8, 2026, 12:06 a.m.
PDg Predicate description generation batch_69fd2a2095f88190bfcbcb2973516ffc completed May 8, 2026, 12:11 a.m.
Created at: May 1, 2026, 12:25 a.m.