Triple

T36529315
Position Surface form Disambiguated ID Type / Status
Subject Anuraag E900395 entity
Predicate hasEmotionalStory P11859 FINISHED
Object yes 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: yes | Statement: [Anuraag, hasEmotionalStory, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmotionalStory
Context triple: [Anuraag, hasEmotionalStory, yes]
  • A. emotionalTrajectory
    Indicates how an entity’s emotional state changes or progresses over time in relation to another entity or context.
  • B. hasInfluentialStory
    Indicates that one entity possesses or is associated with a story that significantly shapes, impacts, or guides the beliefs, actions, or development of another entity.
  • C. hasNarrative chosen
    Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
  • D. hasEmotionalDimension
    Indicates that something involves, expresses, or affects emotions as a significant aspect of its nature or impact.
  • E. hasTraditionalStory
    Indicates that one entity possesses, is associated with, or is the source or subject of a traditional story related to the other 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_69f76e5eedb88190a393b8c623f71dd7 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1b91fd88190ab85afd626603769 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:11 p.m.