Triple

T34009234
Position Surface form Disambiguated ID Type / Status
Subject Rockin' Chair (recording with Gene Krupa Orchestra) E872060 entity
Predicate hasSoloist P86915 FINISHED
Object Roy Eldridge NE NERFINISHED

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: Roy Eldridge | Statement: [Rockin' Chair (recording with Gene Krupa Orchestra), hasSoloist, Roy Eldridge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSoloist
Context triple: [Rockin' Chair (recording with Gene Krupa Orchestra), hasSoloist, Roy Eldridge]
  • A. hasNotableSoloFor
    Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
  • B. isSoloPerformance
    Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
  • C. soloist chosen
    Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
  • D. hasSoloAlbum
    Indicates that an individual has released at least one music album as a solo artist, separate from any group or band projects.
  • E. hasImprovisedSoloBy
    Indicates that an improvised solo performance is attributed to or performed by a specific 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_69f349a08848819084b348d64c1879c3 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: May 1, 2026, 1:51 a.m.