Triple

T13961858
Position Surface form Disambiguated ID Type / Status
Subject Glad to Be Unhappy E335814 entity
Predicate hasNotableInterpretationIn P112425 FINISHED
Object jazz 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: jazz | Statement: [Glad to Be Unhappy, hasNotableInterpretationIn, jazz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableInterpretationIn
Context triple: [Glad to Be Unhappy, hasNotableInterpretationIn, jazz]
  • A. notableInterpretation
    Indicates that an entity is a significant or widely recognized interpretation, rendition, or version of another work, concept, or subject.
  • B. notableInterpretationBy
    Indicates that an entity has a significant or widely recognized interpretation, analysis, or reading provided by a particular agent (such as a person, group, or source).
  • C. containsInterpretationOf
    Indicates that one entity includes or embodies an interpretation or understanding of another entity.
  • D. hasNotablePhrase
    Indicates that an entity is associated with a specific phrase or expression that is considered notable or characteristic of it.
  • E. hasCulturalInterpretation
    Indicates that something is understood, represented, or given meaning within a particular cultural context or tradition.
  • 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_69d81c61f3508190aaf2ca0dc0002c59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e7c73d48190b8e02971b5a8ed5f completed April 14, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69de05a3ccf88190b45c742db483fa08 completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de239524688190a0f2408c239cfcaa completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:18 p.m.