Triple

T29472337
Position Surface form Disambiguated ID Type / Status
Subject Белое солнце пустыни E747543 entity
Predicate роль P268 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. role chosen
    Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
  • B. როლები
    Indicates that an entity has specific roles, functions, or positions assigned or associated with it in a given context.
  • C. themeRole
    Indicates that an entity is the primary participant undergoing or affected by the action or event expressed by a predicate.
  • D. roleInText
    Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
  • E. actorRole
    Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
  • 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_69f66bd2451c8190ad14604068f308d8 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:58 p.m.