Triple

T19992147
Position Surface form Disambiguated ID Type / Status
Subject The Intelligence of Emotions E494088 entity
Predicate hasPartInUnderlyingWork P95131 FINISHED
Object theoretical analysis of emotions 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: theoretical analysis of emotions | Statement: [The Intelligence of Emotions, hasPartInUnderlyingWork, theoretical analysis of emotions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPartInUnderlyingWork
Context triple: [The Intelligence of Emotions, hasPartInUnderlyingWork, theoretical analysis of emotions]
  • A. hasParentWork
    Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
  • B. hasWorkPart chosen
    Indicates that one work is a component, section, or constituent part of another, larger work.
  • C. hasWorkUsedBy
    Indicates that a work (such as a resource, document, or artifact) is utilized or referenced by another entity in performing its activities or functions.
  • D. hasPart
    Indicates that one entity is a component, segment, or constituent part of another entity.
  • E. hasPartnerInWork
    Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fe10ffc81908c94168b0a8ea9c9 completed April 20, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69e537fd311881908448f2aea8b4812e completed April 19, 2026, 8:15 p.m.
Created at: April 11, 2026, 3:31 p.m.