Triple
T30847120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Biches |
E785666
|
entity |
| Predicate | balletsRussesProductionNumber |
P170559
|
FINISHED |
| Object | late Diaghilev period work |
—
|
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: late Diaghilev period work | Statement: [Les Biches, balletsRussesProductionNumber, late Diaghilev period work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletsRussesProductionNumber Context triple: [Les Biches, balletsRussesProductionNumber, late Diaghilev period work]
-
A.
balletsRussesProduction
Indicates that one entity is a production created or staged by the Ballets Russes company in relation to another entity.
-
B.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
C.
balletTitle
Indicates that the subject has the specified title as the name of a ballet.
-
D.
premieredInBallet
Indicates that a work or performance had its first public presentation specifically in the context of a ballet production.
-
E.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
- F. None of above. chosen
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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917961ec81908dbd73e67c1ff383 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:46 p.m.