Triple

T3125795
Position Surface form Disambiguated ID Type / Status
Subject The New Workout Plan E65292 entity
Predicate featuresSpokenInterludes P9713 FINISHED
Object true 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: true | Statement: [The New Workout Plan, featuresSpokenInterludes, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuresSpokenInterludes
Context triple: [The New Workout Plan, featuresSpokenInterludes, true]
  • A. isSpokenAlong
    Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
  • B. includesSpokenEpilogue chosen
    Indicates that the work contains a spoken epilogue segment delivered after the main content concludes.
  • C. includesSpokenPrologue
    Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
  • D. speechContent
    Indicates that one entity expresses, conveys, or contains the spoken or written content associated with another entity’s act of speaking or communication.
  • E. speakerFeatures
    Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given 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_69ad8580c72481909672d37acf647893 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada52e9f348190aa15b2c0d252719f completed March 8, 2026, 4:34 p.m.
PD Predicate disambiguation batch_69ad9df62e548190b053e1478deed467 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:04 p.m.