Triple

T21854697
Position Surface form Disambiguated ID Type / Status
Subject Litwack E539592 entity
Predicate hasVariant P455 FINISHED
Object Litvak 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: Litvak | Statement: [Litwack, hasVariant, Litvak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Litvak
Context triple: [Litwack, hasVariant, Litvak]
  • A. Litvak chosen
    Litvak is a surname most notably borne by Anatole Litvak, a Ukrainian-born film director who worked extensively in Hollywood and Europe.
  • B. Rivkele
    Rivkele is a mythic figure associated with the God of Vengeance, embodying retribution and divine justice.
  • C. Matorf
    Matorf is a district or locality within the town of Lemgo in the German state of North Rhine-Westphalia.
  • D. Avromani
    Avromani is an alternative name for the Gorani people, a Slavic Muslim ethnic group primarily inhabiting the Gora region in the Balkans.
  • E. Avromani
    Avromani is an alternative name for the Hewrami (Hawrami) variety of the Gorani language spoken by Kurdish communities in the Hawraman region of western Iran and northeastern Iraq.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0bd5ba9288190af962117124f6483 completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:56 p.m.