Triple

T5348144
Position Surface form Disambiguated ID Type / Status
Subject Cotton Tail E124105 entity
Predicate hasImprovisationBasis P22740 FINISHED
Object tenor saxophone chorus by Ben Webster 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: tenor saxophone chorus by Ben Webster | Statement: [Cotton Tail, hasImprovisationBasis, tenor saxophone chorus by Ben Webster]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasImprovisationBasis
Context triple: [Cotton Tail, hasImprovisationBasis, tenor saxophone chorus by Ben Webster]
  • A. hasImprovisedSoloBy
    Indicates that an improvised solo performance is attributed to or performed by a specific entity.
  • B. isFrequentlyImprovisedOver chosen
    Indicates that one thing commonly serves as the underlying basis or structure over which improvisation is often performed.
  • C. reasonForImprovisation
    Indicates that one event, condition, or factor serves as the cause or motivation for an improvisational action or behavior.
  • D. hasMusical
    Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
  • E. hasProceduralInstrument
    Indicates that a procedure or process is carried out using, or with the aid of, a specified instrument or tool.
  • 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_69bd464be27081908807b40b75c1bbae completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd85ef75148190815461c2a49302e9 completed March 20, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69bd845c6f108190832a8d14b356368a completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:01 p.m.