Triple

T8271262
Position Surface form Disambiguated ID Type / Status
Subject Kulik E193432 entity
Predicate hasNotableBearer P458 FINISHED
Object Oleksandr Kulik
Oleksandr Kulik is a person notable enough to be recognized as a prominent bearer of the surname Kulik.
 E754188 NE FINISHED

How this triple was built (4 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: Oleksandr Kulik | Statement: [Kulik, hasNotableBearer, Oleksandr Kulik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Oleksandr Kulik
Context triple: [Kulik, hasNotableBearer, Oleksandr Kulik]
  • A. Oleg Kulik
    Oleg Kulik is a Russian performance artist best known for his provocative “man-dog” performances that explore themes of dehumanization, power, and social control.
  • B. Dmitry Kulik
    Dmitry Kulik is a notable individual who shares the surname Kulik, recognized as a distinguished bearer of that name.
  • C. Pavel Kulik
    Pavel Kulik is a person notable enough to be recognized as a bearer of the surname Kulik.
  • D. Piotr Kulik
    Piotr Kulik is a person bearing the Polish surname Kulik, though no widely documented public information distinguishes him as a notable figure.
  • E. Sergei Kulik
    Sergei Kulik is a Russian individual notable enough to be recognized as a bearer of the surname Kulik, though specific widely known public achievements or roles are not clearly documented.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Oleksandr Kulik
Triple: [Kulik, hasNotableBearer, Oleksandr Kulik]
Generated description
Oleksandr Kulik is a person notable enough to be recognized as a prominent bearer of the surname Kulik.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Oleksandr Kulik
Target entity description: Oleksandr Kulik is a person notable enough to be recognized as a prominent bearer of the surname Kulik.
  • A. Oleg Kulik
    Oleg Kulik is a Russian performance artist best known for his provocative “man-dog” performances that explore themes of dehumanization, power, and social control.
  • B. Dmitry Kulik
    Dmitry Kulik is a notable individual who shares the surname Kulik, recognized as a distinguished bearer of that name.
  • C. Pavel Kulik
    Pavel Kulik is a person notable enough to be recognized as a bearer of the surname Kulik.
  • D. Piotr Kulik
    Piotr Kulik is a person bearing the Polish surname Kulik, though no widely documented public information distinguishes him as a notable figure.
  • E. Sergei Kulik
    Sergei Kulik is a Russian individual notable enough to be recognized as a bearer of the surname Kulik, though specific widely known public achievements or roles are not clearly documented.
  • F. None of above. chosen

Provenance (5 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_69ca82e14ae481908ffdb822cd2192bc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7986f8cc8190a529dda980dd6e98 completed March 31, 2026, 7:36 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf422648208190beaa6eaef4173f21 completed April 3, 2026, 4:29 a.m.
NEDg Description generation batch_69cf43bd0f8c8190be2f7dc86f1e76e1 completed April 3, 2026, 4:36 a.m.
NED2 Entity disambiguation (via description) batch_69cf444c9cb08190a37f34faa4a3458d completed April 3, 2026, 4:38 a.m.
Created at: March 30, 2026, 5:50 p.m.