Triple
T30807136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Танец Феи Драже |
E784533
|
entity |
| Predicate | инструмент в оркестровке |
P170519
|
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.
orchestralRole
Indicates the specific function or position an entity holds within an orchestra (e.g., conductor, principal violin, section player).
-
B.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
C.
isOrchestral
Indicates that something involves, is written for, or is performed by an orchestra.
-
D.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
E.
orchestration
Indicates the coordination and arrangement of multiple components or processes to work together harmoniously toward a unified outcome.
- F. None of above. chosen
Provenance (4 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:43 p.m.