Triple
T11980471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coppélia |
E285142
|
entity |
| Predicate | balletRepertoryStatus |
P70653
|
FINISHED |
| Object | standard classical repertory |
—
|
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: standard classical repertory | Statement: [Coppélia, balletRepertoryStatus, standard classical repertory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletRepertoryStatus Context triple: [Coppélia, balletRepertoryStatus, standard classical repertory]
-
A.
publicRepertoireStatus
chosen
Indicates that an entity’s repertoire or collection is designated as publicly visible or accessible rather than private or restricted.
-
B.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
C.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
D.
balletsRussesProduction
Indicates that one entity is a production created or staged by the Ballets Russes company in relation to another entity.
-
E.
balletCompany
Indicates that one entity is a ballet company associated with, representing, or responsible for another entity (such as a performance, dancer, or production).
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.