Triple
T30807151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Танец Феи Драже |
E784533
|
entity |
| Predicate | связанный персонаж |
P88683
|
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.
fictionalCharacterAssociatedWith
chosen
Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
-
B.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
C.
связан с персонажами
Indicates that something has a connection or association with certain characters.
-
D.
gắnVớiNhânVật
Indicates a relationship in which something is associated, connected, or tied to a particular character or person.
-
E.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:43 p.m.