Triple
T29510428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tschaikovsky Piano Concerto No. 2 |
E748632
|
entity |
| Predicate | balletWorldName |
P90424
|
FINISHED |
| Object | Ballet Imperial |
—
|
NE NERFINISHED |
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: Ballet Imperial | Statement: [Tschaikovsky Piano Concerto No. 2, balletWorldName, Ballet Imperial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletWorldName Context triple: [Tschaikovsky Piano Concerto No. 2, balletWorldName, Ballet Imperial]
-
A.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
B.
balletTitle
chosen
Indicates that the subject has the specified title as the name of a ballet.
-
C.
notableBallet
Indicates that there is a notable or significant ballet associated with the subject.
-
D.
balletInclusion
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
-
E.
hasBalletMaster
Indicates that an entity is associated with or overseen by a specific ballet master responsible for its ballet-related training, direction, or instruction.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:31 p.m.