Triple

T6057784
Position Surface form Disambiguated ID Type / Status
Subject Cassidy E134957 entity
Predicate hasLivePerformanceCharacteristic P3288 FINISHED
Object extended improvisational sections 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: extended improvisational sections | Statement: [Cassidy, hasLivePerformanceCharacteristic, extended improvisational sections]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLivePerformanceCharacteristic
Context triple: [Cassidy, hasLivePerformanceCharacteristic, extended improvisational sections]
  • A. livePerformanceFeature
    Indicates that one entity is included or highlighted as a component of another entity’s live performance.
  • B. hasNotableLivePerformancesBy
    Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
  • C. livePerformanceStapleFor chosen
    Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
  • D. hasPerformedLiveIn
    Indicates that an entity has given a live performance in a specified location or venue.
  • E. hasLiveMusic
    Indicates that a place or event features live musical performances as part of its offerings.
  • 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_69c00877b6d4819096b0e163728b73a3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0570d00e88190b2d8d596e40378d9 completed March 22, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69c049edc6f0819092ca620d9073ad26 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:09 p.m.