Triple

T17819112
Position Surface form Disambiguated ID Type / Status
Subject Burt Grusinsky E444927 entity
Predicate familyName P18 FINISHED
Object Grusinsky
Grusinsky is a surname of likely Eastern European or Russian origin.
 E1289569 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: Grusinsky | Statement: [Burt Grusinsky, familyName, Grusinsky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Grusinsky
Context triple: [Burt Grusinsky, familyName, Grusinsky]
  • A. Yezernitsky
    Yezernitsky is a Jewish surname most notably associated with Yitzhak Shamir, the former Prime Minister of Israel, who was born Yitzhak Yezernitsky.
  • B. Svechin
    Svechin is a Russian surname most notably associated with military theorist Aleksandr Svechin.
  • C. Khoyski
    Khoyski is the surname of an Azerbaijani noble and political family best known for Fatali Khan Khoyski, the first Prime Minister of the Azerbaijan Democratic Republic.
  • D. Tolbukhin
    Tolbukhin is a Russian surname most notably associated with Soviet military commander Fyodor Tolbukhin, a prominent general during World War II.
  • E. Menzhinsky
    Menzhinsky is a Russian surname most notably associated with Vyacheslav Menzhinsky, a prominent early Soviet state security official and head of the OGPU.
  • 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: Grusinsky
Triple: [Burt Grusinsky, familyName, Grusinsky]
Generated description
Grusinsky is a surname of likely Eastern European or Russian origin.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Grusinsky
Target entity description: Grusinsky is a surname of likely Eastern European or Russian origin.
  • A. Yezernitsky
    Yezernitsky is a Jewish surname most notably associated with Yitzhak Shamir, the former Prime Minister of Israel, who was born Yitzhak Yezernitsky.
  • B. Svechin
    Svechin is a Russian surname most notably associated with military theorist Aleksandr Svechin.
  • C. Khoyski
    Khoyski is the surname of an Azerbaijani noble and political family best known for Fatali Khan Khoyski, the first Prime Minister of the Azerbaijan Democratic Republic.
  • D. Tolbukhin
    Tolbukhin is a Russian surname most notably associated with Soviet military commander Fyodor Tolbukhin, a prominent general during World War II.
  • E. Menzhinsky
    Menzhinsky is a Russian surname most notably associated with Vyacheslav Menzhinsky, a prominent early Soviet state security official and head of the OGPU.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e488812df081909771d51c54c405fe completed April 19, 2026, 7:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a02ff6630a08190b907c773c77149bb completed May 12, 2026, 10:22 a.m.
NEDg Description generation batch_6a03004cb0048190bf6891754474e317 completed May 12, 2026, 10:26 a.m.
NED2 Entity disambiguation (via description) batch_6a0300bda62081908e6da214147079c2 completed May 12, 2026, 10:28 a.m.
Created at: April 10, 2026, 10:15 a.m.