Triple
T32362414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymonda, Op. 57 |
E826898
|
entity |
| Predicate | balletCulture |
P172243
|
FINISHED |
| Object | Russian ballet |
—
|
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: Russian ballet | Statement: [Raymonda, Op. 57, balletCulture, Russian ballet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletCulture Context triple: [Raymonda, Op. 57, balletCulture, Russian ballet]
-
A.
balletTradition
chosen
Indicates a relationship where an entity is associated with, follows, or embodies a particular tradition or established practice within the art and culture of ballet.
-
B.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
C.
balletInclusion
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
-
D.
balletMusic
Indicates that the music is composed for, associated with, or used in the performance of a ballet.
-
E.
notableBallet
Indicates that there is a notable or significant ballet associated with the subject.
- 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_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:49 a.m.