Triple
T30807130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Танец Феи Драже |
E784533
|
entity |
| Predicate | номер акта |
P170518
|
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.
hasNumberInActa
Indicates that an entity is associated with a specific identifying number recorded in an official acta (formal record or document).
-
B.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
C.
admissionAct
Indicates the act or event of formally allowing or accepting someone or something into a place, group, institution, or state.
-
D.
annexNumber
Indicates that one entity is identified as an annex or supplementary numbered part associated with another entity.
-
E.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
- 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.