Triple

T32588633
Position Surface form Disambiguated ID Type / Status
Subject Prélude à l’après-midi d’un faune E832996 entity
Predicate notableBalletAdaptationCompany P84424 FINISHED
Object Ballets Russes E41277 NE 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: Ballets Russes | Statement: [Prélude à l’après-midi d’un faune, notableBalletAdaptationCompany, Ballets Russes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableBalletAdaptationCompany
Context triple: [Prélude à l’après-midi d’un faune, notableBalletAdaptationCompany, Ballets Russes]
  • A. notableBallet
    Indicates that there is a notable or significant ballet associated with the subject.
  • B. balletCompany
    Indicates that one entity is a ballet company associated with, representing, or responsible for another entity (such as a performance, dancer, or production).
  • C. hasBalletAdaptation
    Indicates that one entity has been adapted into a ballet based on it.
  • D. balletsRussesProduction chosen
    Indicates that one entity is a production created or staged by the Ballets Russes company in relation to another entity.
  • E. balletCompanyAssociation
    Indicates an affiliation or formal relationship between an entity and a ballet company, such as membership, employment, or representation.
  • F. None of above.

Provenance (4 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_69f34929ff648190aded9424aa7564ae completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037cad051c8190b28b354b89208574 completed May 12, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a347baa865481908c792a8fa01b3135 completed June 18, 2026, 11:13 p.m.
PD Predicate disambiguation batch_6a0379f0cbe481909b4b8fc6cbe297f0 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:04 a.m.