Triple

T29510425
Position Surface form Disambiguated ID Type / Status
Subject Tschaikovsky Piano Concerto No. 2 E748632 entity
Predicate originalDesignIntent P41372 FINISHED
Object homage to the Mariinsky Theatre tradition 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: homage to the Mariinsky Theatre tradition | Statement: [Tschaikovsky Piano Concerto No. 2, originalDesignIntent, homage to the Mariinsky Theatre tradition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalDesignIntent
Context triple: [Tschaikovsky Piano Concerto No. 2, originalDesignIntent, homage to the Mariinsky Theatre tradition]
  • A. hasDesignIntent
    Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
  • B. hasDesignOrigin
    Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
  • C. overallDesignGoal
    Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
  • D. designedWith
    Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
  • E. reasonForDesign chosen
    Indicates that one entity serves as the explanation, motivation, or justification for why another entity was designed or created in a particular way.
  • 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_69f0bd461c208190bec20bbf24e02cc5 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69ffa15d53208190ab8574d6c7913e18 completed May 9, 2026, 9:04 p.m.
PD Predicate disambiguation batch_69ff9eee681c81909434e79c627cb528 completed May 9, 2026, 8:54 p.m.
Created at: April 28, 2026, 4:31 p.m.