Triple
T30807129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Танец Феи Драже |
E784533
|
entity |
| Predicate | произведение |
P89775
|
FINISHED |
| Object | «Щелкунчик» |
—
|
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: «Щелкунчик» | Statement: [Танец Феи Драже, произведение, «Щелкунчик»]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: произведение Context triple: [Танец Феи Драже, произведение, «Щелкунчик»]
-
A.
hasDramatizationOf
Indicates that one work or performance is a dramatized adaptation or representation of another source work or event.
-
B.
musicalWork
chosen
Indicates a relationship where an entity is identified as a musical composition or piece associated with another entity (such as a creator, performance, or recording).
-
C.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
D.
producedRecording
Indicates that one entity served as the producer responsible for creating or overseeing the making of a particular recording.
-
E.
creativeWorkType
Indicates the specific category or form of a creative work (such as book, movie, painting, or song) that characterizes the relationship.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903f52948190a9177a14145f6274 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:43 p.m.