Triple
T29471930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Служебный роман |
E747531
|
entity |
| Predicate | режиссёр |
P255
|
FINISHED |
| Object | Эльдар Рязанов |
—
|
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: Эльдар Рязанов | Statement: [Служебный роман, режиссёр, Эльдар Рязанов]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: режиссёр Context triple: [Служебный роман, режиссёр, Эльдар Рязанов]
-
A.
director
chosen
Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
-
B.
directorDescribedAs
Indicates that a director is characterized or portrayed using a particular description, label, or set of attributes.
-
C.
directorSince
Indicates that one entity has held the role of director for another entity starting from a specified point in time.
-
D.
castingDirectorOf
Indicates that a person serves as the casting director responsible for selecting the cast of a particular production or project.
-
E.
directors
Indicates that one entity serves as a director (or is on the board) of another entity, such as an organization or company.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66babf5e08190b8e1007546f3881a |
completed | May 2, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:57 p.m.