Triple
T29842536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moor (Petrushka) |
E757839
|
entity |
| Predicate | firstPerformanceCompanyOfWork |
P19971
|
FINISHED |
| Object | Ballets Russes |
—
|
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: Ballets Russes | Statement: [The Moor (Petrushka), firstPerformanceCompanyOfWork, Ballets Russes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceCompanyOfWork Context triple: [The Moor (Petrushka), firstPerformanceCompanyOfWork, Ballets Russes]
-
A.
firstPerformanceCompany
chosen
Indicates the company that first performed or premiered a given work or production.
-
B.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
C.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
D.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
E.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: April 29, 2026, 5:40 p.m.