Triple

T13514735
Position Surface form Disambiguated ID Type / Status
Subject Fugue in A-flat major, BWV 862 E322729 entity
Predicate hasCompanionWorkType P104843 FINISHED
Object prelude and fugue pair 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: prelude and fugue pair | Statement: [Fugue in A-flat major, BWV 862, hasCompanionWorkType, prelude and fugue pair]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCompanionWorkType
Context triple: [Fugue in A-flat major, BWV 862, hasCompanionWorkType, prelude and fugue pair]
  • A. hasWorkTypeRelation chosen
    Indicates a relationship specifying the type or category of work associated with an entity.
  • B. hasCompanionOrganization
    Indicates that one organization is associated with another organization that accompanies, supports, or partners it in some related capacity.
  • C. hasCompanionPieceType
    Indicates that one item is associated with another as a companion piece of a specified type or role.
  • D. hasPartnerInWork
    Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
  • E. hasCompanionCandidate
    Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf87ca288190a147fbdb2f90985f completed April 12, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69dbae0b63748190b5e207f84b2532ea completed April 12, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:44 p.m.