Triple

T32362385
Position Surface form Disambiguated ID Type / Status
Subject Raymonda, Op. 57 E826898 entity
Predicate balletMasterAtPremiere P52382 FINISHED
Object Marius Petipa 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: Marius Petipa | Statement: [Raymonda, Op. 57, balletMasterAtPremiere, Marius Petipa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: balletMasterAtPremiere
Context triple: [Raymonda, Op. 57, balletMasterAtPremiere, Marius Petipa]
  • A. premieredInBallet
    Indicates that a work or performance had its first public presentation specifically in the context of a ballet production.
  • B. hasBalletMaster chosen
    Indicates that an entity is associated with or overseen by a specific ballet master responsible for its ballet-related training, direction, or instruction.
  • C. artisticDirectorAtPremiere
    Indicates that a person served as the artistic director for a work or production specifically at its premiere event.
  • D. precededByInBallet
    Indicates that one ballet element (such as a step, pose, or sequence) occurs immediately before another in the choreographic order.
  • E. balletTitle
    Indicates that the subject has the specified title as the name of a ballet.
  • 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_69f34915a2588190bb3178f5ec2f48f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6be9866448190b9225dd383e52ec8 completed May 3, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69f6ba6cef208190bc5cd43d96127004 completed May 3, 2026, 3:01 a.m.
Created at: May 1, 2026, 12:49 a.m.