Triple

T30574162
Position Surface form Disambiguated ID Type / Status
Subject Сатин E778197 entity
Predicate рольВПроизведении P23263 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. actorRole
    Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
  • B. featuresCharacterRole chosen
    Indicates that a work includes a character appearing in a specific narrative or functional role.
  • C. theaterRole
    Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
  • D. creditedRoleOf
    Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
  • E. roleInScene
    Indicates that an entity participates in a particular scene with a specific role or function within that scene.
  • 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_69f2249f8c148190ae7eb3912cde112a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f689167878819093cb4f58efd47e2e completed May 2, 2026, 11:30 p.m.
PD Predicate disambiguation batch_69f67e42d6688190b60e91d2c388c555 completed May 2, 2026, 10:44 p.m.
Created at: April 29, 2026, 8:22 p.m.