Triple

T19426530
Position Surface form Disambiguated ID Type / Status
Subject Études-tableaux, Op. 33 E485992 entity
Predicate intendedPerformerLevel P100059 FINISHED
Object virtuoso pianist 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: virtuoso pianist | Statement: [Études-tableaux, Op. 33, intendedPerformerLevel, virtuoso pianist]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedPerformerLevel
Context triple: [Études-tableaux, Op. 33, intendedPerformerLevel, virtuoso pianist]
  • A. intendedPlayerLevel chosen
    Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
  • B. targetPerformanceLevel
    Indicates the specific performance standard or level that an entity is expected or required to achieve.
  • C. intendedForPerformanceBy
    Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
  • D. qualificationLevel
    Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
  • E. eligiblePerformers
    Indicates that certain entities are qualified or permitted to perform in a specified event, role, or 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63219f27481909fe686209defc971 completed April 20, 2026, 2:03 p.m.
PD Predicate disambiguation batch_69e4fd6e806081909053f325ba01ab6b completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:37 p.m.